linux.git/arch/microblaze/kernel/reset.c, branch v6.6.131

microblaze: Explicitly include correct DT includes

2023-07-17T06:22:42+00:00

The DT of_device.h and of_platform.h date back to the separate
of_platform_bus_type before it as merged into the regular platform bus.
As part of that merge prepping Arm DT support 13 years ago, they
"temporarily" include each other. They also include platform_device.h
and of.h. As a result, there's a pretty much random mix of those include
files used throughout the tree. In order to detangle these headers and
replace the implicit includes with struct declarations, users need to
explicitly include the correct includes.

Signed-off-by: Rob Herring 
Link: https://lore.kernel.org/r/20230714174023.4039938-1-robh@kernel.org
Signed-off-by: Michal Simek

microblaze: Switch to standard restart handler

2019-09-19T08:43:32+00:00

The microblaze uses the legacy APIs to dig out a GPIO pin
defined in the root of the device tree to issue a hard
reset of the platform.

Asserting a hard reset should be done using the standard
DT-enabled and fully GPIO descriptor aware driver in
drivers/power/reset/gpio-restart.c using the bindings
from Documentation/devicetree/bindings/power/reset/gpio-restart.txt

To achieve this, first make sure microblaze makes use of
the standard kernel restart path utilizing do_kernel_restart()
from . Put in some grace time and an
emergency print if the restart does not properly assert.

As this is basic platform functionality we patch the DTS
file and defconfig in one go for a lockstep change.

Cc: Arnd Bergmann 
Cc: Michal Simek 
Signed-off-by: Linus Walleij 
[ Michal: Move machine_restart back to reset.c ]
Signed-off-by: Michal Simek

microblaze: consolidate GPIO reset handling

2018-06-21T11:57:39+00:00

Now that platform.c only has the GPIO reset handling left, move the
initcall to reset.c and remove platform.c.

Cc: Michal Simek 
Signed-off-by: Rob Herring 
Signed-off-by: Michal Simek

microblaze: Remove unused prom header from reset.c

2015-01-05T11:36:42+00:00

Completely unused header by this file.

Signed-off-by: Michal Simek

microblaze: Show message when reset gpio is not present

2013-09-04T15:01:37+00:00

Signed-off-by: Michal Simek

microblaze: Prefer to use pr_XXX instead of printk(KERN_XX)

2012-10-04T13:00:32+00:00

Fix reset.c, timer.c, setup.c file.

Signed-off-by: Michal Simek

microblaze: Improve failure handling for GPIO reset

2012-10-04T12:23:42+00:00

Early exit from of_platform_reset_gpio_probe() if there
was no GPIO reset line configured.

Avoid kernel oops in gpio_system_reset():

[   27.413294] Restarting system.
[   27.415674] Machine restart...
[   27.418787] Oops: kernel access of bad area, sig: 11
[   27.423252]  Registers dump: mode=83871D1C
[   27.427428]  r1=00000000, r2=00000000, r3=FFFFFEF8, r4=00000000
[   27.433310]  r5=C026AED0, r6=00000001, r7=00000068, r8=00000000
[   27.439189]  r9=C3871DAC, r10=000011A5, r11=00000000, r12=0000000A
[   27.445318]  r13=00000000, r14=0000000F, r15=C00029BC, r16=00000000
[   27.451558]  r17=C011DE8C, r18=80000115, r19=0000000F, r20=48184ED8
[   27.457770]  r21=00000000, r22=FFFFFFEA, r23=00000001, r24=FEE1DEAD
[   27.463982]  r25=00000054, r26=1000B1C8, r27=00000000, r28=00000000
[   27.470208]  r29=00000000, r30=00000000, r31=C32D30C0, rPC=C011DE8C
[   27.476433]  msr=000042A2, ear=0000004B, esr=00000872, fsr=342E3732

And remove useless dump_stack from machine_restart.

Signed-off-by: Stephan Linz 
Signed-off-by: Michal Simek

gpio/microblaze: Eliminate duplication of of_get_named_gpio_flags()

2011-12-12T20:40:16+00:00

of_reset_gpio_handle() is largely a cut-and-paste copy of
of_get_named_gpio_flags(). There really isn't any reason for the
split, so this patch deletes the duplicate function

Signed-off-by: Grant Likely 
Cc: Michal Simek

of/gpio: stop using device_node data pointer to find gpio_chip

2010-07-05T22:14:30+00:00

Currently the kernel uses the struct device_node.data pointer to resolve
a struct gpio_chip pointer from a device tree node.  However, the .data
member doesn't provide any type checking and there aren't any rules
enforced on what it should be used for.  There's no guarantee that the
data stored in it actually points to an gpio_chip pointer.

Instead of relying on the .data pointer, this patch modifies the code
to add a lookup function which scans through the registered gpio_chips
and returns the gpio_chip that has a pointer to the specified
device_node.

Signed-off-by: Grant Likely 
CC: Andrew Morton 
CC: Anton Vorontsov 
CC: Grant Likely 
CC: David Brownell 
CC: Bill Gatliff 
CC: Dmitry Eremin-Solenikov 
CC: Benjamin Herrenschmidt 
CC: Jean Delvare 
CC: linux-kernel@vger.kernel.org
CC: devicetree-discuss@lists.ozlabs.org

of/gpio: Kill of_gpio_chip and add members directly to gpio_chip

2010-07-05T22:14:30+00:00

The OF gpio infrastructure is great for describing GPIO connections within
the device tree.  However, using a GPIO binding still requires changes to
the gpio controller just to add an of_gpio structure.  In most cases, the
gpio controller doesn't actually need any special support and the simple
OF gpio mapping function is more than sufficient.  Additional, the current
scheme of using of_gpio_chip requires a convoluted scheme to maintain
1:1 mappings between of_gpio_chip and gpio_chip instances.

If the struct of_gpio_chip data members were moved into struct gpio_chip,
then it would simplify the processing of OF gpio bindings, and it would
make it trivial to use device tree OF connections on existing gpiolib
controller drivers.

This patch eliminates the of_gpio_chip structure and moves the relevant
fields into struct gpio_chip (conditional on CONFIG_OF_GPIO).  This move
simplifies the existing code and prepares for adding automatic device tree
support to existing drivers.

Signed-off-by: Grant Likely 
Cc: Andrew Morton 
Cc: Anton Vorontsov 
Cc: Grant Likely 
Cc: David Brownell 
Cc: Bill Gatliff 
Cc: Dmitry Eremin-Solenikov 
Cc: Benjamin Herrenschmidt 
Cc: Jean Delvare