From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] mfd: rohm-bd71828: Add power off functionality
Date: Mon, 25 Mar 2024 14:28:33 +0100 [thread overview]
Message-ID: <20240325142833.538993c2@aktux> (raw)
In-Reply-To: <81bf6604-9160-4bae-8da6-7034f8aa3f92@gmail.com>
Hi Matti,
On Mon, 25 Mar 2024 14:44:43 +0200
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> Hi Andreas,
>
> On 3/25/24 14:16, Andreas Kemnade wrote:
> > On Mon, 25 Mar 2024 13:31:15 +0200
> > Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> >
> >> On 3/24/24 22:12, Andreas Kemnade wrote:
> >>> Since the chip can power off the system, add the corresponding
> >>> functionality.
> >>> Based on https://github.com/kobolabs/Kobo-Reader/raw/master/hw/imx6sll-clara2e/kernel.tar.bz2
> >>> No information source about the magic numbers found.
> >>
> >> Oh, interesting repository :) Thanks for linking to it! I didn't know
> >> someone had reworked this driver...
> >>
> > which btw: contains this interesting snippet (output from fdtdump)
> > bd71828-i2c@4b {
> > reg = <0x0000004b>;
> > compatible = "rohm,bd71828";
> > gpio_int = <0x00000008 0x00000013 0x00000001>;
> > gpio_wdogb = <0x00000039 0x00000018 0x00000001>;
> > #address-cells = <0x00000001>;
> > #size-cells = <0x00000000>;
> > pmic@4b {
> > compatible = "rohm,bd71828";
> > regulators {
> > BUCK1 {
> > regulator-name = "buck1";
> >
> >
> > and to make it work since basically no regulators are registered
> > instead just some regmap_write()s are done to configure something
> > in probe(). It is a pitfall to think that the information below pmic@4b
> > is used, especially since it is not that obvious in the source.
>
> Just to ensure there will be no misunderstanding - I have not authored
> the modifications seen in "Kobo-Reader" repository. Upstream driver does
> register the regulators - and it does not use the oddly named gpio_int
> or the gpio_wdogb:
yes, I know it is not from you and I know the general quality in those repos.
But I feel not well pointing to those repositories without issuing the warning
that regulator information in dtb is not an authoritative source for required
regulator settings. Not that someone enables the smoke-generator
functionality...
But lets not go too much offtopic.
Regards,
Andreas
next prev parent reply other threads:[~2024-03-25 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 20:12 [RFC PATCH 0/2] mfd: rohm-bd71828: Add power off Andreas Kemnade
2024-03-24 20:12 ` [RFC PATCH 1/2] dt-bindings: mfd: Add ROHM BD71828 system-power-controller property Andreas Kemnade
2024-03-25 12:13 ` Krzysztof Kozlowski
2024-03-24 20:12 ` [RFC PATCH 2/2] mfd: rohm-bd71828: Add power off functionality Andreas Kemnade
2024-03-25 11:31 ` Matti Vaittinen
2024-03-25 12:16 ` Andreas Kemnade
2024-03-25 12:44 ` Matti Vaittinen
2024-03-25 13:28 ` Andreas Kemnade [this message]
2024-03-25 14:10 ` Lee Jones
2024-03-25 16:51 ` Lee Jones
2024-03-25 20:14 ` Andreas Kemnade
2024-03-25 12:13 ` Krzysztof Kozlowski
2024-03-25 20:21 ` Andreas Kemnade
2024-03-26 6:32 ` Krzysztof Kozlowski
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=20240325142833.538993c2@aktux \
--to=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).