Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Mark Brown <broonie@kernel.org>,
	Sean Anderson <sean.anderson@linux.dev>,
	"Dhanunjanrao, Katta" <katta.dhanunjanrao@amd.com>,
	"Sagar, Vishal" <vishal.sagar@amd.com>
Cc: 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,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 2/2] ASoC: xilinx: xlnx_i2s: Discover parameters from registers
Date: Fri, 30 Jan 2026 09:19:26 +0100	[thread overview]
Message-ID: <7aa5b8c1-1d54-4d40-8822-5e79d0fdc4b5@amd.com> (raw)
In-Reply-To: <06b3d7e0-27b5-433c-85db-23e4c5ef5472@sirena.org.uk>

+Katta, Vishal

On 1/29/26 19:46, Mark Brown wrote:
> On Thu, Jan 29, 2026 at 01:17:45PM -0500, Sean Anderson wrote:
>> On 1/29/26 13:09, Mark Brown wrote:
> 
>>>> - Driver authors tend to use them even when there are hardware registers
>>>>    available with the same information, as Xilinx has not always been
>>>>    consistent in adding such registers.
> 
>>> I'm not sure I follow your second point - driver authors tend to use
>>> what?
> 
>> Authors look at the devicetree node and see something like
> 
>> 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.

Let me add our driver owner of this device to answer some questions.

Katta: Can you please look at it?

Thanks,
Michal

  reply	other threads:[~2026-01-30  8:19 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 [this message]
2026-02-02 17:52             ` Peter Korsgaard
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=7aa5b8c1-1d54-4d40-8822-5e79d0fdc4b5@amd.com \
    --to=michal.simek@amd.com \
    --cc=broonie@kernel.org \
    --cc=katta.dhanunjanrao@amd.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sean.anderson@linux.dev \
    --cc=tiwai@suse.com \
    --cc=vincenzo.frascino@arm.com \
    --cc=vishal.sagar@amd.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