devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Vladimir Zapolskiy <vz@mleia.com>,
	Russell King <linux@armlinux.org.uk>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	"J.M.B. Downing" <jonathan.downing@nautel.com>,
	Arnd Bergmann <arnd@arndb.de>, Chancel Liu <chancel.liu@nxp.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 1/4] ASoC: dt-bindings: lpc32xx: Add lpc32xx i2s DT binding
Date: Mon, 17 Jun 2024 17:48:42 +0200	[thread overview]
Message-ID: <2fe7ba36-05b9-42c7-8726-ea891cfc7afc@kernel.org> (raw)
In-Reply-To: <CAG+cZ06kzikieaD_JCBybwWk8XKZQjJxa34Cg4QHxrxpT+j0eA@mail.gmail.com>

On 17/06/2024 16:04, Piotr Wojtaszczyk wrote:
>>
>>> It's used by snd_soc_dai_init_dma_data() in [PATCH v3 4/4] to give the
>>> dmaengine a
>>> hint which dma config to use. The LPC32xx doesn't have yet a dmamux driver like
>>
>> and if I change driver platform data to foo and bar, does the DTS work? No.
> 
> They shouldn't change the same way as expected dma-names shouldn't change.
> Lots of drivers expect the dma-names to be "rx", "tx"
> 
>>
>>> lpc18xx-dmamux.c therefore it still uses platform data entries for
>>> pl08x dma channels
>>> and 'SND_DMAENGINE_PCM_FLAG_NO_DT | SND_DMAENGINE_PCM_FLAG_COMPAT'
>>> flags in the devm_snd_dmaengine_pcm_register().
>>> Typically instead of this platform data you would use regular 'dma'
>>> and 'dma-names' if it had
>>> proper dmamux driver like lpc18xx-dmamux.c
>>
>> Exactly. Use these.
> 
> Then I need to write a lpc32xx dma mux driver, device tree binding for
> it and adjust the
> LPC32xx I2S driver for it. Is this a hard requirement to accept this
> patch set for the
> legacy LPC32xx SoC?

I do not see at all analogy with dma-names. dma-names are used ONLY by
the consumer to pick up proper property "dmas" from DT. They are not
passed to DMA code. They are not used to configure DMA provider at all.

You parse string from DT and pass it further as DMA filtering code. This
is abuse of hardware description for programming your driver and their
dependencies.

Why you cannot hard-code them?

Sorry, to be clear: NAK

> 
>>
>>>
>>>>
>>>> Drop.
>>>>
>>>>
>>>>> +
>>>>> +  "#sound-dai-cells":
>>>>> +    const: 0
>>>>> +
>>>
>>> The "dai-common.yam" doesn't declare a default value for this so
>>
>> Where is my comment to which you refer to? Please do not drop context
>> from replies. I have no clue what you want to discuss here.
> Well I didn't remove the context, you said:
> "
> Drop.
> (...)
> +  "#sound-dai-cells":
> +    const: 0
> "
> So I'm confused whether the "#sound-dai-cells" should be in the dt
> binding or not.

??? Drop is above the text so why do you refer to dai cells? We use here
text-based mailing list style of discussions, not corporate MS Office.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-17 15:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH] ASoC: fsl: Add i2s and pcm drivers for LPC32xx CPUs>
2024-06-11  9:47 ` [Patch v2 1/2] ASoC: fsl: Add i2s and pcm drivers for LPC32xx CPUs Piotr Wojtaszczyk
2024-06-11  9:47   ` [Patch v2 2/2] ASoC: dt-bindings: lpc32xx: Add lpc32xx i2s DT binding Piotr Wojtaszczyk
2024-06-11 10:18     ` Krzysztof Kozlowski
2024-06-12  8:02       ` Piotr Wojtaszczyk
2024-06-13  6:11         ` Krzysztof Kozlowski
2024-06-11 10:37     ` Mark Brown
2024-06-11 10:45     ` Krzysztof Kozlowski
2024-06-12  8:06       ` Piotr Wojtaszczyk
2024-06-13  6:11         ` Krzysztof Kozlowski
2024-06-11 11:31     ` Rob Herring (Arm)
2024-06-11 10:15   ` [Patch v2 1/2] ASoC: fsl: Add i2s and pcm drivers for LPC32xx CPUs Krzysztof Kozlowski
2024-06-12  7:48     ` Piotr Wojtaszczyk
2024-06-11 10:36   ` Mark Brown
2024-06-12  7:54     ` Piotr Wojtaszczyk
2024-06-14 16:24     ` Piotr Wojtaszczyk
2024-06-14 16:42       ` Mark Brown
2024-06-14 16:46         ` Piotr Wojtaszczyk
2024-06-14 16:51           ` Mark Brown
2024-06-14 16:34   ` [PATCH v3 0/4] Add audio support for LPC32XX CPUs Piotr Wojtaszczyk
2024-06-14 16:34     ` [PATCH v3 1/4] ASoC: dt-bindings: lpc32xx: Add lpc32xx i2s DT binding Piotr Wojtaszczyk
2024-06-15 10:01       ` Krzysztof Kozlowski
2024-06-17  9:33         ` Piotr Wojtaszczyk
2024-06-17 12:14           ` Krzysztof Kozlowski
2024-06-17 14:04             ` Piotr Wojtaszczyk
2024-06-17 15:48               ` Krzysztof Kozlowski [this message]
2024-06-17 16:30                 ` Piotr Wojtaszczyk
2024-06-14 16:34     ` [PATCH v3 2/4] ARM: dts: lpc32xx: Add missing properties for the i2s interfaces Piotr Wojtaszczyk
2024-06-14 16:34     ` [PATCH v3 3/4] ARM: lpc32xx: Add pl08x virtual dma channels for spi and i2s Piotr Wojtaszczyk
2024-06-14 16:34     ` [PATCH v3 4/4] ASoC: fsl: Add i2s and pcm drivers for LPC32xx CPUs Piotr Wojtaszczyk
2024-06-17 19:30       ` Markus Elfring
2024-06-18  7:45         ` Piotr Wojtaszczyk
2024-06-14 16:43     ` [PATCH v3 0/4] Add audio support for LPC32XX CPUs 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=2fe7ba36-05b9-42c7-8726-ea891cfc7afc@kernel.org \
    --to=krzk@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=chancel.liu@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathan.downing@nautel.com \
    --cc=krzk+dt@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=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=perex@perex.cz \
    --cc=piotr.wojtaszczyk@timesys.com \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.com \
    --cc=vz@mleia.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;
as well as URLs for NNTP newsgroup(s).