From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Igor Paunovic <royalnet026@gmail.com>
Cc: sashiko-reviews@lists.linux.dev, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, kernel@collabora.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] dt-bindings: media: snps,dw-hdmi-rx: add #sound-dai-cells
Date: Wed, 15 Jul 2026 21:20:11 +0200 [thread overview]
Message-ID: <alfcy_rcmjrKJb0H@venus> (raw)
In-Reply-To: <CAEWPSH6L79Kb9wQna9Cg8yGMJAN88__PwsuXvA+oo+fPStLoYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Hi Igor,
On Wed, Jul 15, 2026 at 07:41:22PM +0200, Igor Paunovic wrote:
> Hello Sebastian,
>
> > Not implementing all features in the driver is perfectly fine.
> > Ideally you return -ENOTSUP if somebody tries to use the S/PDIF
> > DAI interface instead of I2S.
>
> Done for v2: the codec registration now exposes the S/PDIF DAI as
> well, so the DAI indexes match the binding (0 = I2S, 1 = S/PDIF),
> and hw_params() rejects the S/PDIF interface with -EOPNOTSUPP until
> that path is actually wired up.
Sounds good to me.
Greetings,
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-15 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 5:19 [RFC PATCH 0/2] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-15 5:19 ` [RFC PATCH 1/2] dt-bindings: media: snps,dw-hdmi-rx: add #sound-dai-cells Igor Paunovic
[not found] ` <20260715055448.AEA021F000E9@smtp.kernel.org>
2026-07-15 6:55 ` Royal Net
2026-07-15 12:59 ` Sebastian Reichel
2026-07-15 13:19 ` Igor Paunovic
2026-07-15 17:27 ` Sebastian Reichel
2026-07-15 17:41 ` Igor Paunovic
2026-07-15 19:20 ` Sebastian Reichel [this message]
2026-07-15 5:19 ` [RFC PATCH 2/2] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-15 19:07 ` Dmitry Osipenko
2026-07-15 19:27 ` Igor Paunovic
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=alfcy_rcmjrKJb0H@venus \
--to=sebastian.reichel@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=royalnet026@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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