public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Jacky Bai <ping.bai@nxp.com>
Cc: sudeep.holla@arm.com, linus.walleij@linaro.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	cristian.marussi@arm.com, aisheng.dong@nxp.com,
	festevam@gmail.com, kernel@pengutronix.de,
	linux-gpio@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org
Subject: Re: [PATCH RFC] pinctrl: freescale: Add support for imx943 pinctrl
Date: Tue, 22 Apr 2025 17:01:50 +0800	[thread overview]
Message-ID: <20250422090150.GB10830@nxa18884-linux> (raw)
In-Reply-To: <20250401072725.1141083-1-ping.bai@nxp.com>

On Tue, Apr 01, 2025 at 03:27:25PM +0800, Jacky Bai wrote:
>Add support for i.MX943 pinctrl.

Let's expand the commit log a bit:

"
i.MX943 System Manager(SM) firmware supports System Control Management
Interface(SCMI) pinctrl protocol as i.MX95 SM. But i.MX943 IOMUXC
Daisy input register base is at a different address compared with i.MX95. So,
update pinctrl-imx-scmi to allow i.MX943 and add daisy off register, and
update pinctrl-scmi to block i.MX943
"

Then, Reviewed-by: Peng Fan <peng.fan@nxp.com> 

In future, we may no need to expand the array list in both drivers,
as of now, we are still exploring how. So the patch is ok for now.

Thanks,
Peng.


  parent reply	other threads:[~2025-04-22  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  7:27 [PATCH RFC] pinctrl: freescale: Add support for imx943 pinctrl Jacky Bai
2025-04-15  7:53 ` Linus Walleij
2025-04-18  7:46   ` Jacky Bai
2025-04-22  9:01 ` Peng Fan [this message]
2025-04-23  9:53   ` Jacky Bai

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=20250422090150.GB10830@nxa18884-linux \
    --to=peng.fan@oss.nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=ping.bai@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sudeep.holla@arm.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