From: Brandon Brnich <b-brnich@ti.com>
To: <linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Nas Chung <nas.chung@chipsnmedia.com>,
Jackson Lee <jackson.lee@chipsnmedia.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
Robert Beckett <bob.beckett@collabora.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nishanth Menon <nm@ti.com>, Darren Etheridge <detheridge@ti.com>,
Brandon Brnich <b-brnich@ti.com>
Subject: [PATCH v2 1/2] dt-bindings: media: Remove K3 Family Prefix from Compatible
Date: Wed, 6 Dec 2023 12:52:53 -0600 [thread overview]
Message-ID: <20231206185254.1748473-2-b-brnich@ti.com> (raw)
In-Reply-To: <20231206185254.1748473-1-b-brnich@ti.com>
K3 family prefix is not included in other TI compatible strings. Remove
this prefix to keep naming convention consistent.
Fixes: de4b9f7e371a ("dt-bindings: media: wave5: add yaml devicetree bindings")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Closes: https://lore.kernel.org/all/CAMuHMdUYOq=q1j=d+Eac28hthOUAaNUkuvxmRu-mUN1pLKq69g@mail.gmail.com/
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
---
Bindings currently reside in linux-next, meaning that the ABI will not be
broken with the removal of K3 prefix. Important to get this merged in
prior to being moved to master so that K3 prefix does not need to be
permanately included.
Documentation/devicetree/bindings/media/cnm,wave521c.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/cnm,wave521c.yaml b/Documentation/devicetree/bindings/media/cnm,wave521c.yaml
index 6d5569e77b7a..471840e858c9 100644
--- a/Documentation/devicetree/bindings/media/cnm,wave521c.yaml
+++ b/Documentation/devicetree/bindings/media/cnm,wave521c.yaml
@@ -17,7 +17,7 @@ properties:
compatible:
items:
- enum:
- - ti,k3-j721s2-wave521c
+ - ti,j721s2-wave521c
- const: cnm,wave521c
reg:
--
2.34.1
next prev parent reply other threads:[~2023-12-06 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 18:52 [PATCH v2 0/2] Update Wave521c Compatible for TI Devices Brandon Brnich
2023-12-06 18:52 ` Brandon Brnich [this message]
2023-12-06 18:57 ` [PATCH v2 1/2] dt-bindings: media: Remove K3 Family Prefix from Compatible Krzysztof Kozlowski
2023-12-06 21:37 ` Nishanth Menon
2023-12-07 12:44 ` Nishanth Menon
2023-12-06 18:52 ` [PATCH v2 2/2] media: chips-media: wave5: Remove K3 References Brandon Brnich
2023-12-06 19:55 ` Nicolas Dufresne
2023-12-06 21:37 ` Nishanth Menon
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=20231206185254.1748473-2-b-brnich@ti.com \
--to=b-brnich@ti.com \
--cc=bob.beckett@collabora.com \
--cc=conor+dt@kernel.org \
--cc=dafna.hirschfeld@collabora.com \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hverkuil-cisco@xs4all.nl \
--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=nicolas.dufresne@collabora.com \
--cc=nm@ti.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