public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Stefano Babic <sbabic@denx.de>,
	Fabio Estevam <festevam@gmail.com>,
	 "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>
Cc: u-boot@lists.denx.de, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH v3 17/17] gpio: adp5585: Update compatible string
Date: Thu, 09 Jan 2025 11:29:18 +0800	[thread overview]
Message-ID: <20250109-imx-bootstd-v3-17-16e5fc0baecf@nxp.com> (raw)
In-Reply-To: <20250109-imx-bootstd-v3-0-16e5fc0baecf@nxp.com>

From: 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>
---
 drivers/gpio/adp5585_gpio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpio/adp5585_gpio.c b/drivers/gpio/adp5585_gpio.c
index ea0cb75459b741c0157aa9077c44163b3c0cab01..114583b3c3bd9a51fbe1960b7532150d0d7cabdd 100644
--- a/drivers/gpio/adp5585_gpio.c
+++ b/drivers/gpio/adp5585_gpio.c
@@ -224,7 +224,7 @@ static int adp5585_probe(struct udevice *dev)
 }
 
 static const struct udevice_id adp5585_ids[] = {
-	{ .compatible = "adp5585" },
+	{ .compatible = "adi,adp5585" },
 	{ }
 };
 

-- 
2.35.3


  parent reply	other threads:[~2025-01-09  2:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  3:29 [PATCH v3 00/17] imx9: switch to bootstd for i.MX93/1 EVK/QSB and i.MX8M EVK Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 01/17] imx: imx93_evk: switch to BOOTSTD Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 02/17] imx: imx93_qsb: " Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 03/17] imx: imx91_evk: " Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 04/17] imx: imx8mp_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 05/17] imx: imx8mp_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 06/17] imx: imx8mn_evk: Cleanup headers Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 07/17] imx: imx8mn_evk: Drop DECLARE_GLOBAL_DATA_PTR Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 08/17] imx: imx8mn_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 09/17] imx: imx8mn_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 10/17] imx: imx8mm_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 11/17] imx: imx8mm_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 12/17] imx: imx8mq_evk: Cleanup headers Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 13/17] imx: imx8mq_evk: Drop DECLARE_GLOBAL_DATA_PTR Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 14/17] imx: imx8mq_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 15/17] imx: imx8mq_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-09  3:29 ` [PATCH v3 16/17] imx: imx93-11x11-evk: drop duplicated nodes Peng Fan (OSS)
2025-01-09  3:29 ` Peng Fan (OSS) [this message]
2025-01-16 14:40 ` [PATCH v3 00/17] imx9: switch to bootstd for i.MX93/1 EVK/QSB and i.MX8M EVK Fabio Estevam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250109-imx-bootstd-v3-17-16e5fc0baecf@nxp.com \
    --to=peng.fan@oss.nxp.com \
    --cc=festevam@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox