u-boot.git/drivers/gpio, branch v2025.04 Unnamed repository; edit this file 'description' to name the repository. gpio: 74x146: depend on DM_SPI 2025-03-04T17:59:51+00:00 J. Neuschäfer j.ne@posteo.net 2025-02-17T11:18:03+00:00 b6f8da1c2e1a91fbf3059bbd68e3355d76c88b42 Currently, Kconfig allows building CONFIG_DM_74X164 without CONFIG_DM_SPI, which results in linker errors because this driver actually uses dm_spi_* functions: drivers/gpio/74x164_gpio.o: in function `gen_74x164_write_conf': undefined reference to `dm_spi_claim_bus' undefined reference to `dm_spi_xfer' undefined reference to `dm_spi_release_bus' Signed-off-by: J. Neuschäfer <j.ne@posteo.net> 
Currently, Kconfig allows building CONFIG_DM_74X164 without
CONFIG_DM_SPI, which results in linker errors because this driver
actually uses dm_spi_* functions:

drivers/gpio/74x164_gpio.o: in function `gen_74x164_write_conf':
  undefined reference to `dm_spi_claim_bus'
  undefined reference to `dm_spi_xfer'
  undefined reference to `dm_spi_release_bus'

Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
Revert "drivers: gpio-uclass: support PMIC GPIO children" 2025-02-12T08:34:04+00:00 Svyatoslav Ryhel clamor95@gmail.com 2024-12-09T10:45:18+00:00 c125ef543c128a3351a564ce584e15e646cdb1df Requesting of PMIC's GPIO child should be done by binding GPIO driver to PMIC's node is GPIO driver does not have its own node. This reverts commit c03cd98d1a163666b4addcdd9a34fc0c77dfd0a5. Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com> 
Requesting of PMIC's GPIO child should be done by binding
GPIO driver to PMIC's node is GPIO driver does not have
its own node.

This reverts commit c03cd98d1a163666b4addcdd9a34fc0c77dfd0a5.

Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
gpio: adp5585: Update compatible string 2025-01-16T13:15:42+00:00 Peng Fan peng.fan@nxp.com 2025-01-09T03:29:18+00:00 2b6601b18e79208ad34b239c225b6cba2e2ddde4 i.MX93-11x11-EVK has switched to use upstream device tree, and use "adi,adp5585". Since i.MX93-11x11-EVK is the only user of this driver, so it is safe to drop "adp5585". Signed-off-by: Peng Fan <peng.fan@nxp.com> 
i.MX93-11x11-EVK has switched to use upstream device tree, and use
"adi,adp5585". Since i.MX93-11x11-EVK is the only user of this driver,
so it is safe to drop "adp5585".

Signed-off-by: Peng Fan <peng.fan@nxp.com>
Merge patch series "Misc. PowerPC MPC83xx fixes/cleanups" 2024-12-30T21:55:33+00:00 Tom Rini trini@konsulko.com 2024-12-30T21:55:33+00:00 ad09ccf7fea365e380d7c7c74e9b87b4c09f30ce J. Neuschäfer <j.ne@posteo.net> says: This patchset contains a few small fixes/cleanups for the MPC83xx platform. Link: https://lore.kernel.org/r/20241220-mpc83xx-misc-v2-0-ff4c17ee5fa4@posteo.net 
J. Neuschäfer <j.ne@posteo.net> says:

This patchset contains a few small fixes/cleanups for the MPC83xx
platform.

Link: https://lore.kernel.org/r/20241220-mpc83xx-misc-v2-0-ff4c17ee5fa4@posteo.net
gpio: mpc8xxx: Preserve pre-init state of outputs 2024-12-30T21:55:27+00:00 J. Neuschäfer j.ne@posteo.net 2024-12-20T10:37:54+00:00 880374542845c0f7cdc4e60a913a987e6ff06b54 The mpc8xxx_gpio driver contains a workaround for certain chips where the previously written state of outputs cannot be read back from the GPIO data (GPDAT) register (MPC8572/MPC8536). This workaround consists of tracking the state of GPDAT in a "shadow register" (i.e. a software variable). The shadow register is initialized to zero. This results in a problem w.r.t. outputs that are configured to a high (1) state before U-Boot runs, but not touched by U-Boot itself: Due to the zero-initialization, these GPIOs end up being set to zero, the first time that any other output is set. To avoid such issues initialize the GPDAT shadow register to the value previously held by any outputs, if possible. On MPC8572/MPC8536 this should make no difference, i.e. the shadow register should be initialized to zero on these chips. This patch has been tested on a MPC8314E-based board. Reviewed-by: Sinan Akman <sinan@writeme.com> Signed-off-by: J. Neuschäfer <j.ne@posteo.net> 
The mpc8xxx_gpio driver contains a workaround for certain chips
where the previously written state of outputs cannot be read back
from the GPIO data (GPDAT) register (MPC8572/MPC8536). This workaround
consists of tracking the state of GPDAT in a "shadow register" (i.e. a
software variable). The shadow register is initialized to zero.

This results in a problem w.r.t. outputs that are configured to a
high (1) state before U-Boot runs, but not touched by U-Boot itself:
Due to the zero-initialization, these GPIOs end up being set to zero,
the first time that any other output is set.

To avoid such issues initialize the GPDAT shadow register to the value
previously held by any outputs, if possible. On MPC8572/MPC8536 this
should make no difference, i.e. the shadow register should be
initialized to zero on these chips.

This patch has been tested on a MPC8314E-based board.

Reviewed-by: Sinan Akman <sinan@writeme.com>
Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
gpio: npcm: Add persist feature to sgpio module 2024-12-30T21:55:01+00:00 Jim Liu jim.t90615@gmail.com 2024-12-10T06:35:05+00:00 787d38935031f951fea4ec33ea0299817f9bd1aa Base on GPIO hog to support sgpio persist enable feature. Signed-off-by: Jim Liu <JJLIU0@nuvoton.com> 
Base on GPIO hog to support sgpio persist enable feature.

Signed-off-by: Jim Liu <JJLIU0@nuvoton.com>
Merge tag 'v2025.01-rc5' into next 2024-12-26T04:31:04+00:00 Tom Rini trini@konsulko.com 2024-12-26T04:31:04+00:00 5cfbf8c3644cc95c3c8b5d2541ed7f32136c0da1 Prepare v2025.01-rc5 
Prepare v2025.01-rc5
gpio: renesas: Fix R-Car spelling 2024-12-11T07:36:24+00:00 Marek Vasut marek.vasut+renesas@mailbox.org 2024-12-11T07:30:28+00:00 4a9c8946b8c1fec28ca696512f639723aa3bec05 The correct spelling is R-Car, including the dash, update the usage. Kconfig strings and comment changes only, no functional change. Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org> 
The correct spelling is R-Car, including the dash, update the usage.
Kconfig strings and comment changes only, no functional change.

Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
gpio: imx_rgpio2p: Move 8ulp_data to data section 2024-12-07T12:07:03+00:00 Peng Fan peng.fan@nxp.com 2024-12-03T15:42:44+00:00 4af5084a3b8e97067b836179667c6d838084faea have_dual_base is set to false, so the 8ulp_data will be put in BSS section which conflicts with the area of u-boot.dtb which padded just after u-boot-nodtb.bin. So move 8ulp_data to data section to avoid its content being corrupted by dtb. Fixes: 51cfa66f2c4 ("gpio: imx_rgpio2p: support one address") Signed-off-by: Peng Fan <peng.fan@nxp.com> 
have_dual_base is set to false, so the 8ulp_data will be put in BSS
section which conflicts with the area of u-boot.dtb which padded just
after u-boot-nodtb.bin. So move 8ulp_data to data section to avoid
its content being corrupted by dtb.

Fixes: 51cfa66f2c4 ("gpio: imx_rgpio2p: support one address")
Signed-off-by: Peng Fan <peng.fan@nxp.com>
dm: gpio: Return error when pull up/down is requested but set_flags ops is not implmentated 2024-12-04T20:11:43+00:00 Zixun LI admin@hifiphile.com 2024-10-21T15:04:51+00:00 3c69a95b9a84f629cb6e5215158f9332a731aae9 Currently in _dm_gpio_set_flags() when set_flags ops is not implemented direction_output()/_input() is used, but pull up/down is not supported by these ops. Signed-off-by: Zixun LI <admin@hifiphile.com> 
Currently in _dm_gpio_set_flags() when set_flags ops is not implemented
direction_output()/_input() is used, but pull up/down is not supported by
these ops.

Signed-off-by: Zixun LI <admin@hifiphile.com>