From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/2] firmware: arm_scmi: introduce max-rx-timeout-ms property
Date: Fri, 21 Jun 2024 20:46:56 +0800 [thread overview]
Message-ID: <20240621-scmi-mailbox-v1-v1-0-8ed450735f46@nxp.com> (raw)
The current mailbox scmi_desc set the timeout value to 30ms, but
each platform might have its own maximum receive channel timeout value
based on the System Control Management Interface(SCMI) firmware design
and hardware attributes, so introduce a property for that and use it.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (2):
dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms
firmware: arm_scmi: set mailbox timeout value from device tree
.../devicetree/bindings/firmware/arm,scmi.yaml | 6 ++++++
drivers/firmware/arm_scmi/driver.c | 19 ++++++++++++++-----
drivers/firmware/arm_scmi/raw_mode.c | 11 +++++++----
drivers/firmware/arm_scmi/raw_mode.h | 3 ++-
4 files changed, 29 insertions(+), 10 deletions(-)
---
base-commit: 76db4c64526c5e8ba0f56ad3d890dce8f9b00bbc
change-id: 20240618-scmi-mailbox-v1-9b2c19663986
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2024-06-21 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 12:46 Peng Fan (OSS) [this message]
2024-06-21 12:46 ` [PATCH 1/2] dt-bindings: firmware: arm,scmi: introduce property mbox-rx-timeout-ms Peng Fan (OSS)
2024-06-27 21:46 ` Rob Herring
2024-06-27 23:17 ` Peng Fan
2024-07-01 9:06 ` Sudeep Holla
2024-07-01 12:41 ` Peng Fan
2024-06-21 12:46 ` [PATCH 2/2] firmware: arm_scmi: set mailbox timeout value from device tree Peng Fan (OSS)
2024-06-28 2:59 ` kernel test robot
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=20240621-scmi-mailbox-v1-v1-0-8ed450735f46@nxp.com \
--to=peng.fan@oss.nxp.com \
--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=robh@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;
as well as URLs for NNTP newsgroup(s).