From: Rob Herring <robh@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: linux-arm-kernel@lists.infradead.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>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
arm-scmi@vger.kernel.org, james.quinlan@broadcom.com,
justin.chen@broadcom.com, kapil.hali@broadcom.com,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 1/2] dt-bindings: sram: Document reg-io-width property
Date: Mon, 12 Aug 2024 10:55:19 -0600 [thread overview]
Message-ID: <20240812165519.GA1260568-robh@kernel.org> (raw)
In-Reply-To: <20240810214621.14417-2-florian.fainelli@broadcom.com>
On Sat, Aug 10, 2024 at 02:46:20PM -0700, Florian Fainelli wrote:
> Some SRAMs need to be accessed with a specific access width, define
> the 'reg-io-width' property specifying such access sizes.
IMO, those SRAMs should have a specific compatible. That restriction
makes them less usable.
OTOH, it is a standard property. Shrug.
>
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
> Documentation/devicetree/bindings/sram/sram.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sram/sram.yaml b/Documentation/devicetree/bindings/sram/sram.yaml
> index 0922d1f71ba8..18e42fb36846 100644
> --- a/Documentation/devicetree/bindings/sram/sram.yaml
> +++ b/Documentation/devicetree/bindings/sram/sram.yaml
> @@ -101,6 +101,12 @@ patternProperties:
> IO mem address range, relative to the SRAM range.
> maxItems: 1
>
> + reg-io-width:
> + description:
> + The size (in bytse) of the IO accesses that should be performed on the
> + SRAM.
> + enum: [1, 2, 4, 8]
> +
> pool:
> description:
> Indicates that the particular reserved SRAM area is addressable
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-08-12 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 21:46 [PATCH 0/2] Support for I/O width within ARM SCMI SHMEM Florian Fainelli
2024-08-10 21:46 ` [PATCH 1/2] dt-bindings: sram: Document reg-io-width property Florian Fainelli
2024-08-11 5:37 ` Christophe JAILLET
2024-08-11 12:39 ` Krzysztof Kozlowski
2024-08-12 16:55 ` Rob Herring [this message]
2024-08-10 21:46 ` [PATCH 2/2] firmware: arm_scmi: Support 'reg-io-width' property for shared memory Florian Fainelli
2024-08-11 2:42 ` Florian Fainelli
2024-08-11 12:17 ` kernel test robot
2024-08-11 12:27 ` kernel test robot
2024-08-11 12:27 ` kernel test robot
2024-08-11 12:42 ` Peng Fan
2024-08-11 21:03 ` Florian Fainelli
2024-08-11 21:08 ` Florian Fainelli
2024-08-12 17:18 ` Cristian Marussi
2024-08-12 17:46 ` Florian Fainelli
2024-08-12 18:01 ` Cristian Marussi
2024-08-12 21:19 ` Florian Fainelli
2024-08-13 5:00 ` Florian Fainelli
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=20240812165519.GA1260568-robh@kernel.org \
--to=robh@kernel.org \
--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=florian.fainelli@broadcom.com \
--cc=james.quinlan@broadcom.com \
--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=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).