From: Rob Herring <robh@kernel.org>
To: Brandon Brnich <b-brnich@ti.com>
Cc: Nas Chung <nas.chung@chipsnmedia.com>,
Jackson Lee <jackson.lee@chipsnmedia.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Darren Etheridge <detheridge@ti.com>
Subject: Re: [PATCH v2] dt-bindings: media: Add sram-size Property for Wave5
Date: Fri, 2 Feb 2024 15:06:59 -0600 [thread overview]
Message-ID: <20240202210659.GA1390727-robh@kernel.org> (raw)
In-Reply-To: <20240201184238.2542695-1-b-brnich@ti.com>
On Thu, Feb 01, 2024 at 12:42:38PM -0600, Brandon Brnich wrote:
> Wave521c has capability to use SRAM carveout to store reference data with
> purpose of reducing memory bandwidth. To properly use this pool, the driver
> expects to have an sram and sram-size node. Without sram-size node, driver
> will default value to zero, making sram node irrelevant.
The mmio-sram binding already defines how to carve up shared SRAM.
Also, sram-size here is property, not a node.
Rob
prev parent reply other threads:[~2024-02-02 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 18:42 [PATCH v2] dt-bindings: media: Add sram-size Property for Wave5 Brandon Brnich
2024-02-02 10:47 ` Krzysztof Kozlowski
2024-02-02 12:52 ` Nishanth Menon
2024-02-02 13:56 ` Krzysztof Kozlowski
2024-02-02 15:58 ` Nishanth Menon
2024-02-02 16:08 ` Krzysztof Kozlowski
2024-02-05 14:12 ` Nishanth Menon
2024-02-05 18:51 ` Andrew Davis
2024-02-05 19:20 ` Brandon Brnich
2024-02-08 6:22 ` Devarsh Thakkar
2024-02-09 17:42 ` Nicolas Dufresne
2024-02-12 10:57 ` Devarsh Thakkar
2024-02-09 17:33 ` Nicolas Dufresne
2024-02-09 17:22 ` Nicolas Dufresne
2024-02-02 21:06 ` Rob Herring [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=20240202210659.GA1390727-robh@kernel.org \
--to=robh@kernel.org \
--cc=b-brnich@ti.com \
--cc=conor+dt@kernel.org \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jackson.lee@chipsnmedia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=nm@ti.com \
--cc=vigneshr@ti.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).