All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Oleksii Moisieiev <oleksii_moisieiev@epam.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-gpio@vger.kernel.org,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Peng Fan <peng.fan@nxp.com>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v5 0/4] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support
Date: Thu, 14 Mar 2024 16:48:24 +0000	[thread overview]
Message-ID: <ZfMqWP-t39SCvkA2@pluto> (raw)
In-Reply-To: <20240314-pinctrl-scmi-v5-0-b19576e557f2@nxp.com>

On Thu, Mar 14, 2024 at 09:35:17PM +0800, Peng Fan (OSS) wrote:
> Since SCMI 3.2 Spec is released, and this patchset has got R-b/T-b,
> is it ok to land this patchset?
> 

I'll have a look at this last version and a spin on my test setup.

...but has this V5 change at all since the Reviewed-by tags due to the
latest spec changes ?

...IOW does this V5 include the latest small bits spec-changes or those
latest gpio-related spec-changes are just not needed at the level of the Linux
pinctrl support as of now and can be added later on when a Linux gpio
driver will be built on top of this ?

Thanks,
Cristian

WARNING: multiple messages have this Message-ID (diff)
From: Cristian Marussi <cristian.marussi@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Oleksii Moisieiev <oleksii_moisieiev@epam.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-gpio@vger.kernel.org,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Peng Fan <peng.fan@nxp.com>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v5 0/4] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support
Date: Thu, 14 Mar 2024 16:48:24 +0000	[thread overview]
Message-ID: <ZfMqWP-t39SCvkA2@pluto> (raw)
In-Reply-To: <20240314-pinctrl-scmi-v5-0-b19576e557f2@nxp.com>

On Thu, Mar 14, 2024 at 09:35:17PM +0800, Peng Fan (OSS) wrote:
> Since SCMI 3.2 Spec is released, and this patchset has got R-b/T-b,
> is it ok to land this patchset?
> 

I'll have a look at this last version and a spin on my test setup.

...but has this V5 change at all since the Reviewed-by tags due to the
latest spec changes ?

...IOW does this V5 include the latest small bits spec-changes or those
latest gpio-related spec-changes are just not needed at the level of the Linux
pinctrl support as of now and can be added later on when a Linux gpio
driver will be built on top of this ?

Thanks,
Cristian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-03-14 16:48 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 13:35 [PATCH v5 0/4] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support Peng Fan (OSS)
2024-03-14 13:35 ` Peng Fan (OSS)
2024-03-14 13:35 ` [PATCH v5 1/4] firmware: arm_scmi: introduce helper get_max_msg_size Peng Fan (OSS)
2024-03-14 13:35   ` Peng Fan (OSS)
2024-03-14 13:35 ` [PATCH v5 2/4] dt-bindings: firmware: arm,scmi: support pinctrl protocol Peng Fan (OSS)
2024-03-14 13:35   ` Peng Fan (OSS)
2024-03-14 15:32   ` Dan Carpenter
2024-03-14 15:32     ` Dan Carpenter
2024-03-14 13:35 ` [PATCH v5 3/4] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support Peng Fan (OSS)
2024-03-14 13:35   ` Peng Fan (OSS)
2024-03-15 16:58   ` Cristian Marussi
2024-03-15 16:58     ` Cristian Marussi
2024-03-21 14:46   ` Dan Carpenter
2024-03-21 14:46     ` Dan Carpenter
2024-03-24 10:45     ` Dan Carpenter
2024-03-24 10:45       ` Dan Carpenter
2024-03-24 12:15       ` Peng Fan
2024-03-24 12:15         ` Peng Fan
2024-03-14 13:35 ` [PATCH v5 4/4] pinctrl: Implementation of the generic scmi-pinctrl driver Peng Fan (OSS)
2024-03-14 13:35   ` Peng Fan (OSS)
2024-03-14 15:31   ` Dan Carpenter
2024-03-14 15:31     ` Dan Carpenter
2024-03-15  0:44     ` Peng Fan
2024-03-15  0:44       ` Peng Fan
2024-03-15  6:24       ` Dan Carpenter
2024-03-15  6:24         ` Dan Carpenter
2024-03-20  9:53   ` Dan Carpenter
2024-03-20  9:53     ` Dan Carpenter
2024-03-14 16:48 ` Cristian Marussi [this message]
2024-03-14 16:48   ` [PATCH v5 0/4] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support Cristian Marussi
2024-03-15  0:31   ` Peng Fan
2024-03-15  0:31     ` Peng Fan
2024-03-15 16:53     ` Cristian Marussi
2024-03-15 16:53       ` Cristian Marussi
2024-03-15 18:20       ` Dan Carpenter
2024-03-15 18:20         ` Dan Carpenter
2024-03-17 19:08         ` Cristian Marussi
2024-03-17 19:08           ` Cristian Marussi
2024-03-18  2:47       ` Peng Fan
2024-03-18  2:47         ` Peng Fan

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=ZfMqWP-t39SCvkA2@pluto \
    --to=cristian.marussi@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksii_moisieiev@epam.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=takahiro.akashi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.