From: Peter Korsgaard <peter@korsgaard.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-sound@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Michal Simek <michal.simek@amd.com>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 2/2] ASoC: xilinx: xlnx_i2s: Discover parameters from registers
Date: Mon, 02 Feb 2026 18:52:27 +0100 [thread overview]
Message-ID: <87jywvvxr8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <06b3d7e0-27b5-433c-85db-23e4c5ef5472@sirena.org.uk> (Mark Brown's message of "Thu, 29 Jan 2026 18:46:23 +0000")
>>>>> "Mark" == Mark Brown <broonie@kernel.org> writes:
Hi,
>> and go "Ah, there are the properties I need." On some Xilinx cores this
>> is the only way to discover certain properties, so people have gotten into
>> the habit of using them even when these properties can be read from the
>> device itself.
> Oh. If the properties are there it's reasonable and sensible to use
> them, them being redundant is a concern when specifying the binding but
> once things are there any discrepency should usually be resolved in
> favour of the binding.
I also think making the hardware registers take priority over the DTS
makes sense (E.G. what this patch does), as the DTS can get out of sync
with the (programmable) HW configuration if the FPGA config is changed
and a DTS update is forgotten.
>> I would rather remove it for the code size reduction and simplication.
> We're talking a couple of function calls with no error handling here,
> I'm not sure anyone concerned about that kind of impact is running
> Linux.
Agreed, but the HW registers should by definition always be in sync with
the IP block configuration, where the DTS update involves a manual
update so it may not, so the HW registers are more reliable than the DTS.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2026-02-02 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 17:23 [PATCH 0/2] ASoC: xilinx: xlnx_i2s: Discover parameters from registers Sean Anderson
2026-01-29 17:23 ` [PATCH 1/2] dt-bindings: sound: xlnx,i2s: Make discoverable parameters optional Sean Anderson
2026-01-29 17:37 ` Conor Dooley
2026-01-29 17:23 ` [PATCH 2/2] ASoC: xilinx: xlnx_i2s: Discover parameters from registers Sean Anderson
2026-01-29 17:27 ` Mark Brown
2026-01-29 17:46 ` Sean Anderson
2026-01-29 18:09 ` Mark Brown
2026-01-29 18:17 ` Sean Anderson
2026-01-29 18:46 ` Mark Brown
2026-01-30 8:19 ` Michal Simek
2026-02-02 17:52 ` Peter Korsgaard [this message]
2026-01-29 19:58 ` Andrew Lunn
2026-01-29 20:13 ` Sean Anderson
2026-01-29 17:37 ` Andrew Lunn
2026-01-29 17:51 ` Sean Anderson
2026-01-30 6:35 ` kernel test robot
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=87jywvvxr8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=perex@perex.cz \
--cc=sean.anderson@linux.dev \
--cc=tiwai@suse.com \
--cc=vincenzo.frascino@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox