From: Lee Jones <lee@kernel.org>
To: Ying Liu <victor.liu@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org
Subject: Re: [PATCH RESEND] mfd: Add Freescale i.MX8qxp Control and Status Registers (CSR) module driver
Date: Mon, 14 Nov 2022 10:03:42 +0000 [thread overview]
Message-ID: <Y3ISftAta+/R711T@google.com> (raw)
In-Reply-To: <AM7PR04MB70467B746B6CA03CD2FB0982983E9@AM7PR04MB7046.eurprd04.prod.outlook.com>
On Wed, 09 Nov 2022, Ying Liu wrote:
> > Yeah, I tried to not to introduce a new driver for the CSR module, but
> > it seems that it is needed.
>
> After more experiments, I think it's appropriate to take the CSR module as a
> simple-pm-bus device instead of a simple-mfd device. This requires to change
> the existing DT bindings for the CSR module and it's child devices. I'll send the
> change out once it is ready. Thanks for Lee's review and comments.
Excellent, well done.
No problem, you're very welcome.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2022-11-14 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221017075702.4182846-1-victor.liu@nxp.com>
[not found] ` <Y1/sUfeVy1a6EKZQ@google.com>
[not found] ` <afa29fcc11436dd957314a4066c9141937f0470c.camel@nxp.com>
[not found] ` <b7bcc99c006c91871f0518c1a132035d2a148f24.camel@nxp.com>
[not found] ` <Y2jKRQ8VyauSfXmH@google.com>
[not found] ` <4dfb7699c33974a682d798071c85b431b87e5432.camel@nxp.com>
2022-11-14 10:01 ` [PATCH RESEND] mfd: Add Freescale i.MX8qxp Control and Status Registers (CSR) module driver Lee Jones
[not found] ` <AM7PR04MB70467B746B6CA03CD2FB0982983E9@AM7PR04MB7046.eurprd04.prod.outlook.com>
2022-11-14 10:03 ` Lee Jones [this message]
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=Y3ISftAta+/R711T@google.com \
--to=lee@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=victor.liu@nxp.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