From: Lee Jones <lee@kernel.org>
To: lgirdwood@gmail.com, broonie@kernel.org, werneazc@gmail.com
Cc: linux-kernel@vger.kernel.org,
Andre Werner <andre.werner@systec-electronic.com>
Subject: Re: (subset) [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from device
Date: Fri, 18 Aug 2023 17:44:43 +0100 [thread overview]
Message-ID: <20230818164443.GD986605@google.com> (raw)
In-Reply-To: <169237658196.1308508.13955700873692765066.b4-ty@kernel.org>
On Fri, 18 Aug 2023, Lee Jones wrote:
> On Fri, 18 Aug 2023 10:37:21 +0200, werneazc@gmail.com wrote:
> > This commit prepares a following commit for the regulator part of the MFD.
> > The driver should support different device chips that differ in their
> > register definitions, for instance to control LDOA1 and SWB2.
> > So it is necessary to use a dedicated regulator description for a
> > specific device variant. Thus, the content from DEVICEID Register 1 is
> > used to choose a dedicated configuration between the different device
> > variants.
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] mfd: (tps65086): Read DEVICE ID register 1 from device
> commit: c957aecacc831c00497ee95c6984e319f7f82229
Note that this is not the correct subject format for this subsystem.
Patch on test - will send a PR for Mark to pull once complete.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-08-18 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:37 [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from device werneazc
2023-08-18 8:37 ` [PATCH v2 2/2] regulator: (tps65086): Select dedicated regulator config for chip variant werneazc
2023-08-18 16:36 ` (subset) [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from device Lee Jones
2023-08-18 16:44 ` Lee Jones [this message]
2023-08-18 20:45 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.6 merge window Lee Jones
2023-08-21 14:20 ` [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from device 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=20230818164443.GD986605@google.com \
--to=lee@kernel.org \
--cc=andre.werner@systec-electronic.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=werneazc@gmail.com \
/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