From: Mark Brown <broonie@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Satya Priya <quic_c_skakit@quicinc.com>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_collinsd@quicinc.com,
quic_subbaram@quicinc.com, quic_jprakash@quicinc.com
Subject: Re: [PATCH V9 4/6] regulator: Add a regulator driver for the PM8008 PMIC
Date: Wed, 6 Apr 2022 18:27:44 +0100 [thread overview]
Message-ID: <Yk3NkNK3e+fgj4eG@sirena.org.uk> (raw)
In-Reply-To: <CAE-0n53O23=N0zkZpg87Q3EyKquLe3WLNJT8qnZz4WEor6QK7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
On Wed, Apr 06, 2022 at 10:21:01AM -0700, Stephen Boyd wrote:
> Quoting Mark Brown (2022-04-06 09:36:14)
> > On Wed, Apr 06, 2022 at 08:51:48AM -0700, Stephen Boyd wrote:
> > > My guess is that this is one IC that responds to multiple i2c addresses.
> > > The "main" qcom,pm8008 address is 0x8 and that supports things like
> > > interrupts. Then there's an address for regulators at 0x9 which controls
> > > the handful of LDOs on the PMIC.
> > So it's like the TI TWL4030 and Palmas - in which case it should
> > probably be handled similarly?
> How did those work out? I wasn't involved and I don't know what you
> mean. Do they have multiple i2c addresses they respond to?
Yes, exactly. The main device uses i2c_new_dummy_device() to
instantiate the extras when it probes. See twl-core.c
>
> > Note that the original sumbission was
> > *also* a MFD subfunction, but using a DT compatible to match the
> > platform device - this is the first I've heard of this being a separate
> > I2C function.
> I'm mainly looking at the dts file now. It clearly has two i2c devices
> at 0x8 and 0x9. Maybe the regulator driver followed the mfd design
> because the first driver for this device is an mfd.
I'm guessing from the naming that they're also externally described as
the same device - presumably it's two dies shoved together in the same
package for some reason without being otherwise joined up. Is the
second device geniunely regulators only or does it have anything else
bundled in there?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-06 19:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:50 [PATCH V9 0/6] Add Qualcomm Technologies, Inc. PM8008 regulator driver Satya Priya
2022-04-05 13:50 ` [PATCH V9 1/6] dt-bindings: mfd: pm8008: Add reset-gpios Satya Priya
2022-04-05 19:04 ` Stephen Boyd
2022-04-13 1:50 ` Rob Herring
2022-04-05 13:50 ` [PATCH V9 2/6] dt-bindings: mfd: pm8008: Add pm8008 regulator bindings Satya Priya
2022-04-05 19:05 ` Stephen Boyd
2022-04-13 1:51 ` Rob Herring
2022-04-05 13:50 ` [PATCH V9 3/6] mfd: pm8008: Add mfd cell struct to register LDOs Satya Priya
2022-04-05 19:08 ` Stephen Boyd
2022-04-06 9:19 ` Satya Priya Kakitapalli (Temp)
2022-04-05 13:50 ` [PATCH V9 4/6] regulator: Add a regulator driver for the PM8008 PMIC Satya Priya
2022-04-05 14:17 ` Mark Brown
2022-04-06 9:06 ` Satya Priya Kakitapalli (Temp)
2022-04-05 19:09 ` Stephen Boyd
2022-04-06 7:31 ` Mark Brown
2022-04-06 15:23 ` Stephen Boyd
2022-04-06 15:45 ` Mark Brown
2022-04-06 15:51 ` Stephen Boyd
2022-04-06 16:36 ` Mark Brown
2022-04-06 17:21 ` Stephen Boyd
2022-04-06 17:27 ` Mark Brown [this message]
2022-04-06 18:16 ` Stephen Boyd
2022-04-07 5:12 ` Satya Priya Kakitapalli (Temp)
2022-04-06 9:38 ` Satya Priya Kakitapalli (Temp)
2022-04-05 19:09 ` Stephen Boyd
2022-04-06 9:26 ` Satya Priya Kakitapalli (Temp)
2022-04-05 13:50 ` [PATCH V9 5/6] arm64: dts: qcom: pm8008: Add base dts file Satya Priya
2022-04-05 19:11 ` Stephen Boyd
2022-04-06 9:27 ` Satya Priya Kakitapalli (Temp)
2022-04-05 13:50 ` [PATCH V9 6/6] arm64: dts: qcom: sc7280: Add pm8008 support for sc7280-idp Satya Priya
2022-04-05 19:13 ` Stephen Boyd
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=Yk3NkNK3e+fgj4eG@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_c_skakit@quicinc.com \
--cc=quic_collinsd@quicinc.com \
--cc=quic_jprakash@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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