From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
Hugh Cole-Baker <sigmaris@gmail.com>,
ALSA-devel <alsa-devel@alsa-project.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RESEND PATCH v2] drm/bridge: dw-hdmi-i2s: set insert_pcuv bit if hardware supports it
Date: Fri, 13 Sep 2024 22:17:00 -0300 [thread overview]
Message-ID: <ZuTkDMx4qalIFKdH@geday> (raw)
In-Reply-To: <ZuSufaLavkdMdsSL@geday>
On Fri, Sep 13, 2024 at 06:28:34PM -0300, Geraldo Nascimento wrote:
> On Fri, Sep 13, 2024 at 10:12:39PM +0100, Hugh Cole-Baker wrote:
> > I added printk to show the value of AUD_CONF2, and found that on 6.1.23, the
> > value is 0 before the code in this patch sets the insert_pcuv bit. On 6.10.3
> > the value is 4, i.e. insert_pcuv is already set.
> >
> > According to the RK3399 TRM, the value-after-reset of the insert_pcuv bit is 1,
> > so apparently on the 6.1.23 kernel something is clearing the bit after HW reset
> > but before this driver sets the hw_params, and this patch sets it back to the
> > correct value. On 6.10.3 the bit is not cleared, i.e. this patch is seemingly
> > no longer necessary (but is a harmless no-op).
>
> Hi Hugh,
>
> Thank you for your extensive testing. It seems then there's no action we
> need to take for mainline, as it's already fixed there.
Unless Neil wants to pick-up it up for Stable? Neil, although not a
regression, this is definitely a show-stopper for sound on RK3399
for older, still supported kernels. And thanks to Hugh detailed
report we now have confirmation that this happens on vanilla
RK3399 and is not a quirk of my Rock Pi N10 board or sink.
Thanks,
Geraldo Nascimento
next prev parent reply other threads:[~2024-09-14 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 12:04 [RESEND PATCH v2] drm/bridge: dw-hdmi-i2s: set insert_pcuv bit if hardware supports it Geraldo Nascimento
2022-10-31 8:20 ` Neil Armstrong
2022-10-31 21:06 ` Geraldo Nascimento
2024-09-13 21:12 ` Hugh Cole-Baker
2024-09-13 21:28 ` Geraldo Nascimento
2024-09-14 1:17 ` Geraldo Nascimento [this message]
2024-12-30 2:54 ` Geraldo Nascimento
2024-12-30 2:54 ` Geraldo Nascimento
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=ZuTkDMx4qalIFKdH@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=neil.armstrong@linaro.org \
--cc=sigmaris@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.