From: Lee Jones <lee@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
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 16:51:34 +0000 [thread overview]
Message-ID: <20240325165134.GP13211@google.com> (raw)
In-Reply-To: <20240325141032.GO13211@google.com>
On Mon, 25 Mar 2024, Lee Jones wrote:
> On Mon, 25 Mar 2024, Matti Vaittinen 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.
>
> Odd! Not only did I not receive the original patch, I also did not
> receive your response Andreas. Spam is empty too.
>
> LORE too: https://lore.kernel.org/all/?q=%22mfd:%20rohm-bd71828:%20Add%20power%20off%20functionality%22
Super weird! They just all came through.
The LORE link above is now working too.
I suspect an issue with kernel.org.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-03-25 16:51 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
2024-03-25 14:10 ` Lee Jones
2024-03-25 16:51 ` Lee Jones [this message]
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=20240325165134.GP13211@google.com \
--to=lee@kernel.org \
--cc=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=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).