From: sashiko-bot@kernel.org
To: "Arun Iyengar" <aiyengar1990@gmail.com>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: rockchip: i2s-tdm: add the reset value of XFER to the regmap defaults
Date: Tue, 10 Nov 2026 07:36:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-206522@kernel.org> (raw)
In-Reply-To: <20261110-asoc-rockchip-i2s-tdm-v1-2-f32951b3c527@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] ASoC: rockchip: i2s-tdm: missing Fixes trailer for I2S_XFER
reg_default
--
commit fcc3b955539c797b954dd2c22348b8e552e615ec
Author: Arun Iyengar <aiyengar1990@gmail.com>
> ASoC: rockchip: i2s-tdm: add the reset value of XFER to the regmap defaults
>
> I2S_XFER (0x1c) is writeable and not volatile, so it is cached, but it
> has no entry in rockchip_i2s_tdm_reg_defaults[]. The flat cache then
> treats it as uninitialised, and the first cached access of it -- the
> regmap_update_bits() in the trigger and stop paths, or regcache_sync()
> after a runtime suspend -- warns
>
> rockchip-i2s-tdm fddf0000.i2s: using zero-initialized flat cache, this may cause unexpected behavior
>
> It is the only cached register without a default: TXFIFOLR, INTSR, CLR,
> TXDR, RXDR and RXFIFOLR are volatile and all other registers have one.
>
> Add XFER with its reset value of 0 (TX and RX stopped), which is also
> what the zero-initialised cache assumed so far, so no register value
> written to the hardware changes.
>
> Signed-off-by: Arun Iyengar <aiyengar1990@gmail.com>
[Severity: Low]
Since I2S_XFER (0x1c) was omitted from rockchip_i2s_tdm_reg_defaults[]
when the driver was added, should this include a Fixes: tag so stable
trees can pick it up?
Fixes: 081068fd6414 ("ASoC: rockchip: add support for i2s-tdm controller")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-asoc-rockchip-i2s-tdm-v1-0-f32951b3c527@gmail.com?part=2
next prev parent reply other threads:[~2026-11-10 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 7:16 [PATCH 0/2] ASoC: rockchip: i2s-tdm: register the PCM before the DAI Arun Iyengar
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:16 ` [PATCH 1/2] ASoC: rockchip: i2s-tdm: Register " Arun Iyengar
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:16 ` [PATCH 2/2] ASoC: rockchip: i2s-tdm: add the reset value of XFER to the regmap defaults Arun Iyengar
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:16 ` Arun Iyengar via B4 Relay
2026-11-10 7:36 ` sashiko-bot [this message]
2026-11-10 8:37 ` Arun Iyengar
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=sashiko-outbox-206522@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=aiyengar1990@gmail.com \
--cc=linux-sound@vger.kernel.org \
--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 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.