From: Mark Brown <broonie@kernel.org>
To: jeff_chang@richtek.com
Cc: lgirdwood@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] regulator: rt5133: Add RT5133 PMIC regulator Support
Date: Mon, 11 Aug 2025 14:08:16 +0100 [thread overview]
Message-ID: <421d5c9c-bf2c-40d4-b8da-cbfc19d60ff5@sirena.org.uk> (raw)
In-Reply-To: <20250731031701.2832994-2-jeff_chang@richtek.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Thu, Jul 31, 2025 at 11:15:32AM +0800, jeff_chang@richtek.com wrote:
> From: Jeff Chang <jeff_chang@richtek.com>
>
> RT5133 is a highly-integrated chip. It includes 8 LDOs and 3 GPOs that can
> be used to drive output high/low purpose. The dependency of the GPO block is
> internally LDO1 Voltage.
This breaks an allmodconfig build:
/build/stage/linux/drivers/regulator/rt5133-regulator.c:605:15: error: incompati
ble function pointer types assigning to 'int (*)(struct gpio_chip *, unsigned in
t, int)' from 'void (struct gpio_chip *, unsigned int, int)' [-Wincompatible-fun
ction-pointer-types]
605 | priv->gc.set = rt5133_gpio_set;
| ^ ~~~~~~~~~~~~~~~
1 error generated.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-11 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 3:15 [PATCH v6 1/2] regulator: dt-bindings: Add Richtek RT5133 Support jeff_chang
2025-07-31 3:15 ` [PATCH v6 2/2] regulator: rt5133: Add RT5133 PMIC regulator Support jeff_chang
2025-08-11 13:08 ` Mark Brown [this message]
2025-07-31 6:24 ` [PATCH v6 1/2] regulator: dt-bindings: Add Richtek RT5133 Support Krzysztof Kozlowski
2025-08-13 15:24 ` Mark Brown
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=421d5c9c-bf2c-40d4-b8da-cbfc19d60ff5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeff_chang@richtek.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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®