From: Florian Fainelli <florian.fainelli@broadcom.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
arm-scmi@vger.kernel.org (open list:SYSTEM CONTROL &
POWER/MANAGEMENT INTERFACE),
linux-arm-kernel@lists.infradead.org (moderated list:SYSTEM
CONTROL & POWER/MANAGEMENT INTERFACE),
justin.chen@broadcom.com, opendmb@gmail.com,
kapil.hali@broadcom.com, bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH v2 0/2] Support for I/O width within ARM SCMI SHMEM
Date: Tue, 13 Aug 2024 11:07:45 -0700 [thread overview]
Message-ID: <20240813180747.1439034-1-florian.fainelli@broadcom.com> (raw)
We just got our hands on hardware that only supports 32-bit access width
to the SRAM being used. This patch series adds support for the
'reg-io-width' property and allows us to specify the exact access width
that the SRAM supports.
Changes in v2:
- fixed typo in the binding and added reviewed-by tag from Krzysztof
- determine the correct I/O operation at the time we parse the
'reg-io-width' property rather than for each
tx_prepare/fetch_response/fetch_notification call
- dropped support for 1 and 2 bytes 'reg-io-width' as they do not quite
make sense, if we can support such smaller access size, then we can
support the larger 4 byte access width, too, and there are many places
within the SCMI code where ioread32/iowrite32 are used
Florian Fainelli (2):
dt-bindings: sram: Document reg-io-width property
firmware: arm_scmi: Support 'reg-io-width' property for shared memory
.../devicetree/bindings/sram/sram.yaml | 6 ++
drivers/firmware/arm_scmi/common.h | 32 +++++++-
.../arm_scmi/scmi_transport_mailbox.c | 13 ++-
.../firmware/arm_scmi/scmi_transport_optee.c | 10 ++-
.../firmware/arm_scmi/scmi_transport_smc.c | 11 ++-
drivers/firmware/arm_scmi/shmem.c | 81 +++++++++++++++++--
6 files changed, 132 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-13 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 18:07 Florian Fainelli [this message]
2024-08-13 18:07 ` [PATCH v2 1/2] dt-bindings: sram: Document reg-io-width property Florian Fainelli
2024-08-13 19:29 ` Rob Herring (Arm)
2024-08-13 20:08 ` Florian Fainelli
2024-08-13 18:07 ` [PATCH v2 2/2] firmware: arm_scmi: Support 'reg-io-width' property for shared memory Florian Fainelli
2024-08-16 17:02 ` Cristian Marussi
2024-08-16 17:39 ` Florian Fainelli
2024-08-16 17:54 ` Cristian Marussi
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=20240813180747.1439034-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=arm-scmi@vger.kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=justin.chen@broadcom.com \
--cc=kapil.hali@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opendmb@gmail.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