From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Linus Walleij <linusw@kernel.org>, Chen-Yu Tsai <wens@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] pinctrl: axp209: Drop check for disabled devices
Date: Mon, 21 Sep 2026 11:41:46 +0200 [thread overview]
Message-ID: <40e52e7300313b33d7c49e9edea71ec98808c7fd.1789983244.git.ukleinek@debian.org> (raw)
In-Reply-To: <cover.1789983244.git.ukleinek@debian.org>
Since commit 6b5c350648b8 ("mfd: mfd-core: Honour Device Tree's request
to disable a child-device") the mfd core checks for disabled devices, so
there is no use in doing that again in the mfd child driver.
Drop the check.
Signed-off-by: Uwe Kleine-König <ukleinek@debian.org>
---
drivers/pinctrl/pinctrl-axp209.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-axp209.c b/drivers/pinctrl/pinctrl-axp209.c
index 2bd8487484a8..5539ce642b39 100644
--- a/drivers/pinctrl/pinctrl-axp209.c
+++ b/drivers/pinctrl/pinctrl-axp209.c
@@ -442,9 +442,6 @@ static int axp20x_pctl_probe(struct platform_device *pdev)
struct pinctrl_desc *pctrl_desc;
int ret;
- if (!of_device_is_available(pdev->dev.of_node))
- return -ENODEV;
-
if (!axp20x) {
dev_err(&pdev->dev, "Parent drvdata not set\n");
return -EINVAL;
--
2.47.3
next prev parent reply other threads:[~2026-09-21 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:41 [PATCH 0/4] Drive-by changes to axp20x drivers Uwe Kleine-König
2026-09-21 9:41 ` Uwe Kleine-König [this message]
2026-10-01 6:52 ` [PATCH 1/4] pinctrl: axp209: Drop check for disabled devices Linus Walleij
2026-09-21 9:41 ` [PATCH 2/4] power: supply: axp20x*: " Uwe Kleine-König
2026-09-21 9:41 ` [PATCH 3/4] power: supply: axp20x_usb: Introduce a helper variable for &pdev->dev Uwe Kleine-König
2026-09-21 9:41 ` [PATCH 4/4] power: supply: axp20x_usb: Improve probe error reporting Uwe Kleine-König
2026-09-21 13:09 ` [PATCH 0/4] Drive-by changes to axp20x drivers Chen-Yu Tsai
2026-10-04 17:46 ` (subset) " Sebastian Reichel
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=40e52e7300313b33d7c49e9edea71ec98808c7fd.1789983244.git.ukleinek@debian.org \
--to=ukleinek@debian.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wens@kernel.org \
/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
all inboxes | Powered by JetHome®