From: Mark Brown <broonie@kernel.org>
To: Karel Balej <balejk@matfyz.cz>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org,
"Duje Mihanović" <duje.mihanovic@skole.hr>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [RFC PATCH v4 2/5] mfd: add driver for Marvell 88PM886 PMIC
Date: Thu, 21 Mar 2024 19:32:11 +0000 [thread overview]
Message-ID: <f9ff03a0-377e-46ed-b7b1-2f10017a3b1f@sirena.org.uk> (raw)
In-Reply-To: <CZZO2EFTAKN2.246XG441ECYYK@matfyz.cz>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Thu, Mar 21, 2024 at 08:14:44PM +0100, Karel Balej wrote:
> Mark Brown, 2024-03-21T19:00:24+00:00:
> > I would expect that if you have two separate register maps they would
> > have separate configurations that describe the corresponding physical
> > register maps, as far as I can tell this driver is just making up a
> > maximum register number.
> Alright, so I should just use a separate config for each regmap and set
> the max_register value for each to whatever I can find is actually the
> highest used value in the downstream code -- correct?
That sounds plausible if you don't have any other information about the
register maps.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-21 19:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 15:51 [RFC PATCH v4 0/5] initial support for Marvell 88PM886 PMIC Karel Balej
2024-03-11 15:51 ` [RFC PATCH v4 1/5] dt-bindings: mfd: add entry " Karel Balej
2024-03-11 15:51 ` [RFC PATCH v4 2/5] mfd: add driver " Karel Balej
2024-03-21 15:42 ` Lee Jones
2024-03-21 16:12 ` Karel Balej
2024-03-21 16:20 ` Lee Jones
2024-03-21 16:55 ` Karel Balej
2024-03-21 16:58 ` Mark Brown
2024-03-21 17:08 ` Karel Balej
2024-03-21 17:17 ` Mark Brown
2024-03-21 17:32 ` Karel Balej
2024-03-21 17:48 ` Mark Brown
2024-03-21 18:16 ` Karel Balej
2024-03-21 19:00 ` Mark Brown
2024-03-21 19:14 ` Karel Balej
2024-03-21 19:32 ` Mark Brown [this message]
2024-03-11 15:51 ` [RFC PATCH v4 3/5] regulator: add regulators " Karel Balej
2024-03-11 15:51 ` [RFC PATCH v4 4/5] input: add onkey " Karel Balej
2024-03-11 15:51 ` [RFC PATCH v4 5/5] MAINTAINERS: add myself " Karel Balej
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=f9ff03a0-377e-46ed-b7b1-2f10017a3b1f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balejk@matfyz.cz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=duje.mihanovic@skole.hr \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).