From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: linux-media@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
kernel@collabora.com, bob.beckett@collabora.com,
hverkuil-cisco@xs4all.nl, nicolas.dufresne@collabora.com,
nas.chung@chipsnmedia.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 5/6] dt-bindings: media: wave5: add yaml devicetree bindings
Date: Mon, 4 Sep 2023 09:53:09 +0200 [thread overview]
Message-ID: <4b88a31a-bbff-21b5-a53d-19a3e66e2f3e@linaro.org> (raw)
In-Reply-To: <20230904062502.qtajep4zyslnouxv@basti-XPS-13-9310>
On 04/09/2023 08:25, Sebastian Fricke wrote:
>>> + sram:
>>
>> Missing vendor prefix.
>
> After some discussion with the the manufacturer of this CODEC chip, the SRAM
> is not fixed to the CODEC chip but instead part of the SoC, thus the
> vendor can vary. It sounds like the policy is to use the vendor prefix
> of the SoC, that was used for upstreaming. But that policy sounds a bit
> like a potential for future confusion to me, so I wanted to ask what you
> would like to see. The SoC we develop on is from TI and the CODEC chip is from
> C&M, so I could either call it: `ti,sram` or `cnm,sram`
I meant vendor prefix of this device. It does not matter what SoC is
that, however it turns out it is already a generic property, so no
vendor prefix is needed if you use the same property - phandle points to
a node which is a sram.yaml.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-09-04 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221207121350.66217-1-sebastian.fricke@collabora.com>
2022-12-07 12:13 ` [PATCH v11 5/6] dt-bindings: media: wave5: add yaml devicetree bindings Sebastian Fricke
2022-12-07 12:31 ` Krzysztof Kozlowski
2022-12-07 13:17 ` Krzysztof Kozlowski
2022-12-07 15:09 ` Sebastian Fricke
2022-12-07 15:27 ` Krzysztof Kozlowski
2022-12-12 11:32 ` Sebastian Fricke
2023-09-04 6:25 ` Sebastian Fricke
2023-09-04 7:53 ` Krzysztof Kozlowski [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=4b88a31a-bbff-21b5-a53d-19a3e66e2f3e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bob.beckett@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.fricke@collabora.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).