From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andrey Golovko <andrey.golovko@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: sdw-mbq: don't call an unset readable_reg callback
Date: Wed, 12 Aug 2026 10:13:25 +0100 [thread overview]
Message-ID: <anw5NRVk9JYUij2l@opensource.cirrus.com> (raw)
In-Reply-To: <20260811184500.5312-1-andrey.golovko@gmail.com>
On Tue, Aug 11, 2026 at 10:14:35PM +0300, Andrey Golovko wrote:
> regmap_sdw_mbq_poll_busy() decides whether to poll the Function Busy bit
> by calling ctx->readable_reg(), which is a straight copy of
> config->readable_reg. That callback is optional: regmap_readable() treats
> a NULL ->readable_reg as "every register is readable", and drivers rely on
> that. es9356 and tac5xx2-sdw both build an MBQ regmap without one.
>
> Since commit ca1b11b36d82 ("regmap: sdw-mbq: Allow defers on undeferrable
> controls") the poll runs on every -ENODATA, not only for Controls the
> driver marked deferrable, so any of those devices answering
> COMMAND_IGNORED takes the kernel through a NULL function pointer.
>
> Treat a missing callback the way the rest of regmap does and poll.
>
> Fixes: 5bc493bf0c37 ("regmap: sdw-mbq: Add support for SDCA deferred controls")
> Signed-off-by: Andrey Golovko <andrey.golovko@gmail.com>
> ---
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2026-08-12 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 19:14 [PATCH] regmap: sdw-mbq: don't call an unset readable_reg callback Andrey Golovko
2026-08-12 9:13 ` Charles Keepax [this message]
2026-08-12 17:08 ` Mark Brown
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=anw5NRVk9JYUij2l@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andrey.golovko@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@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.