Re: [PATCH v3 1/5] ASoC: dt-bindings: fsl,imx-asrc: update port binding to support multiple paths

Krzysztof Kozlowski <[email protected]>
Newsgroups gmane.linux.sound,gmane.linux.drivers.devicetree,gmane.linux.ports.arm.kernel,gmane.linux.kernel,gmane.linux.ports.ppc64.devel
Message-ID <[email protected]>
On 10/08/2026 21:07, Frank Li wrote:
> On Mon, Aug 10, 2026 at 09:12:20AM +0200, Krzysztof Kozlowski wrote:
>> On Tue, Aug 04, 2026 at 09:39:07AM -0500, Frank Li wrote:
>>> On Tue, Aug 04, 2026 at 06:02:14PM +0800, [email protected] wrote:
>>>> From: Shengjiu Wang <[email protected]>
>>>>
>>>> The i.MX ASRC hardware supports up to three conversion pairs (A, B, C).
>>>> The existing binding exposed only a single generic audio-graph port,
>>>> which cannot represent independent conversion paths when multiple pairs
>>>> are in use simultaneously.
>>>>
>>>> Add a ports container that enumerates up to three sub-ports, each
>>>> representing an independent conversion path:
>>>>   port@0 -- conversion path 0
>>>>   port@1 -- conversion path 1
>>>>   port@2 -- conversion path 2
>>>>
>>>> Each sub-port references audio-graph-port.yaml as before. Hardware pairs
>>>> are allocated dynamically at stream open time; each active stream
>>>> direction (playback or capture) on a port consumes one hardware pair.
>>>>
>>>> For backwards compatibility, keep the old single port property but mark
>>>> it deprecated. A schema constraint (not: required: [port, ports]) ensures
>>>> that both forms cannot be used at the same time. The binding example is
>>>> updated to show the preferred ports form.
>>>>
>>>> No existing upstream DTS file for fsl,imx-asrc uses the previously
>>>> documented single 'port' node, so this change does not break any
>>>> in-tree device tree.
>>>
>>> if no existing upstream DTS file use it, you can direct replace with ports
>>
>> And what about all other users of this binding?
> 
> Kernel is that only known user. Uboot don't use this part.

So other kernels will get broken?

Best regards,
Krzysztof
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.