From: <Hermes.Wu@ite.com.tw>
To: <krzk@kernel.org>
Cc: <mchehab@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <hverkuil+cisco@kernel.org>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <broonie@kernel.org>,
<lgirdwood@gmail.com>, <linux-sound@vger.kernel.org>,
<linux-api@vger.kernel.org>
Subject: RE: [PATCH 1/5] dt-bindings: media: ite,it6625: add audio DAI properties
Date: Thu, 5 Nov 2026 01:50:57 +0000 [thread overview]
Message-ID: <01818606697f4504b67d6f461d04ae57@ite.com.tw> (raw)
In-Reply-To: <20261104-sparkling-icy-hound-fd0dac@quoll>
Hi Krzysztof
>
>-----Original Message-----
>From: Krzysztof Kozlowski <krzk@kernel.org>
>Sent: Wednesday, November 4, 2026 10:24 PM
>To: Hermes Wu (吳佳宏) <Hermes.Wu@ite.com.tw>
>Cc: Mauro Carvalho Chehab <mchehab@kernel.org>; Rob Herring <robh@kernel.org>; Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor Dooley <conor+dt@kernel.org>; Hans Verkuil <hverkuil+cisco@kernel.org>; linux-media@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Mark Brown <broonie@kernel.org>; Liam Girdwood <lgirdwood@gmail.com>; linux-sound@vger.kernel.org; linux-api@vger.kernel.org
>Subject: Re: [PATCH 1/5] dt-bindings: media: ite,it6625: add audio DAI properties
>
>On Tue, Nov 03, 2026 at 02:50:19PM +0800, Hermes Wu wrote:
>> IT6625 and IT6626 decode the HDMI audio stream and output it on an I2S
>> interface, driving the bit and frame clocks themselves. The bridge has
>> up to eight I2S data pins.
>>
>> Add '#sound-dai-cells' so the bridge can be referenced as an audio
>> codec DAI, and 'ite,i2s-data-lanes' to describe which data pins are
>> connected to the audio receiver, in HDMI channel-pair order. Without
>> the property only SD0 is connected.
>>
>> Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
>> ---
>> .../devicetree/bindings/media/i2c/ite,it6625.yaml | 23
>> +++++++++++++++++++++-
>> 1 file changed, 22 insertions(+), 1 deletion(-)
>
>Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Thanks for your review.
>Best regards,
>Krzysztof
>
>
next prev parent reply other threads:[~2026-11-05 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 6:50 [PATCH 0/5] media: i2c: it6625: add HDMI audio capture over I2S Hermes Wu via B4 Relay
2026-11-03 6:50 ` [PATCH 1/5] dt-bindings: media: ite,it6625: add audio DAI properties Hermes Wu via B4 Relay
2026-11-04 14:24 ` Krzysztof Kozlowski
2026-11-05 1:50 ` Hermes.Wu [this message]
2026-11-03 6:50 ` [PATCH 2/5] media: Documentation: it6625: document the audio controls Hermes Wu via B4 Relay
2026-11-03 6:50 ` [PATCH 3/5] media: i2c: it6625: decode audio status fields with FIELD_GET() Hermes Wu via B4 Relay
2026-11-03 6:50 ` [PATCH 4/5] media: i2c: it6625: add I2S audio capture DAI Hermes Wu via B4 Relay
2026-11-03 6:50 ` [PATCH 5/5] media: i2c: it6625: capture compressed and HBR audio, not just LPCM Hermes Wu via B4 Relay
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=01818606697f4504b67d6f461d04ae57@ite.com.tw \
--to=hermes.wu@ite.com.tw \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil+cisco@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®