From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: devicetree@vger.kernel.org, cristian.marussi@arm.com,
Peng Fan <peng.fan@nxp.com>,
sudeep.holla@arm.com, conor+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms
Date: Thu, 11 Jul 2024 15:05:05 -0600 [thread overview]
Message-ID: <172073190412.3008130.10566834515724904100.robh@kernel.org> (raw)
In-Reply-To: <20240709140957.3171255-1-peng.fan@oss.nxp.com>
On Tue, 09 Jul 2024 22:09:56 +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> System Controller Management Interface(SCMI) firmwares might have
> different designs by SCMI firmware developers. So the maximum receive
> channel timeout value might also varies in the various designs.
>
> So introduce property mbox-rx-timeout-ms to let each platform could
> set its own timeout value in device tree.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> V3:
> Add minimum: 1, because 0 is invalid. maximum is not set,
> because it is platform specific and unknown.
> V2:
> Drop defaults, update description.
>
> Documentation/devicetree/bindings/firmware/arm,scmi.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2024-07-11 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:09 Peng Fan (OSS)
2024-07-09 14:09 ` [PATCH V3 2/2] firmware: arm_scmi: set mailbox timeout value from device tree Peng Fan (OSS)
2024-07-18 2:24 ` Peng Fan
2024-07-18 6:11 ` Krzysztof Kozlowski
2024-07-18 6:22 ` Peng Fan
2024-07-30 11:31 ` Cristian Marussi
2024-07-30 14:24 ` Peng Fan
2024-07-30 14:56 ` Cristian Marussi
2024-07-11 21:05 ` Rob Herring (Arm) [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=172073190412.3008130.10566834515724904100.robh@kernel.org \
--to=robh@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--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
all inboxes | Powered by JetHome®