From: Sven Van Asbroeck <thesven73@gmail.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH 1/2] drm/i2c: tda998x: adjust CTS_N audio pre-divider calculation
Date: Fri, 22 Feb 2019 17:29:54 -0500 [thread overview]
Message-ID: <CAGngYiWeKkfdKT_s3op-PRbNgTZbiiva9RO0zJejFmQkoAdo7Q@mail.gmail.com> (raw)
In-Reply-To: <20190222213611.ogahe24h4t37ndhy@shell.armlinux.org.uk>
On Fri, Feb 22, 2019 at 4:36 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
> There's actually two threads of conversation going, and I recently had
> a reply from the maintainer of hdmi-codec suggesting a way forward - so
> I've coded that up as the three RFC patches you should have just
> received.
Thank you, that's awesome !
> It probably would be better to try and find some generic way to deal
> with this.
>
> After all, the I2S source probably knows which ratios it supports.
> Given that many sinks support a limited set of values as well, if
> ASoC core knew the supported set at each end of an I2S DAI format
> link, it could probably select a working bclk ratio automatically.
Agree, possibly the same way the ASoC core auto-matches both sides when they
are connected with a dai_link? Pardon my ignorance.
Of course the auto-matching should only happen when both sides provide a
bclk ratio range - to avoid having to retro-fit every single dai.
prev parent reply other threads:[~2019-02-22 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 18:18 [PATCH 1/2] drm/i2c: tda998x: adjust CTS_N audio pre-divider calculation Sven Van Asbroeck
2019-02-21 18:18 ` [PATCH 2/2] sound: hdmi-codec: propagate physical_width Sven Van Asbroeck
2019-02-22 13:20 ` [PATCH 1/2] drm/i2c: tda998x: adjust CTS_N audio pre-divider calculation Russell King - ARM Linux admin
2019-02-22 15:47 ` Sven Van Asbroeck
2019-02-22 16:27 ` Russell King - ARM Linux admin
2019-02-22 20:16 ` Russell King - ARM Linux admin
2019-02-22 21:18 ` Sven Van Asbroeck
2019-02-22 21:36 ` Russell King - ARM Linux admin
2019-02-22 22:29 ` Sven Van Asbroeck [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=CAGngYiWeKkfdKT_s3op-PRbNgTZbiiva9RO0zJejFmQkoAdo7Q@mail.gmail.com \
--to=thesven73@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=peda@axentia.se \
/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).