[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <591767ee-e349-7a17-a9e9-b95d0500c7c1@linaro.org>
Date: Thu, 2 Jun 2022 09:40:18 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tinghan Shen <tinghan.shen@...iatek.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v1] dt-bindings: dsp: mediatek: add mt8186 dsp document
On 02/06/2022 08:44, Tinghan Shen wrote:
>>> + mbox-names:
>>> + items:
>>> + - const: mbox0
>>> + - const: mbox1
>>
>> These should be rather some meaningful names, e.g. "rx" and "tx".
>
> The mbox name has to align with the adsp ipc driver.
> The adsp ipc driver is using 'mbox%d' for mailbox channels.
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=9db69df4bdd37eb1f65b6931ee067fb15b9a4d5c
>
> chan_name = kasprintf(GFP_KERNEL, "mbox%d", i);
>
> /* ...snip... */
>
> adsp_chan->ch = mbox_request_channel_byname(cl, chan_name);
>
> Is it ok to continue using these names?
It is a bit confusing... how did that driver got merged recently without
bindings? Why bindings are separate?
The bindings always come together in one patchset with the driver
implementing them. Bindings are though a separate patch, yet still
followed by the driver which uses them.
I do not see any compatibles in that driver, which suggests there is no
other binding using it. If that's correct, then you need to change the
driver.
Best regards,
Krzysztof
Powered by blists - more mailing lists