On 13/09/2022 09:14, Chancel Liu wrote: >>> Add a string property to assign ASoC platform driver name. It also >>> represents the rpmsg channel this sound card sits on. This property >>> can be omitted if there is only one sound card and it sits on >>> "rpmsg-audio-channel". >>> >>> Signed-off-by: Chancel Liu <chancel.liu@xxxxxxx> >>> --- >>> .../devicetree/bindings/sound/fsl,rpmsg.yaml | 34 +++++++++++++++++-- >>> 1 file changed, 32 insertions(+), 2 deletions(-) >>> >>> diff --git a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml >> b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml >>> index d370c98a62c7..35e3cb9f768b 100644 >>> --- a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml >>> +++ b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml >>> @@ -11,8 +11,11 @@ maintainers: >>> >>> description: | >>> fsl_rpmsg is a virtual audio device. Mapping to real hardware devices >>> - are SAI, DMA controlled by Cortex M core. What we see from Linux >>> - side is a device which provides audio service by rpmsg channel. >>> + are SAI, MICFIL, DMA controlled by Cortex M core. What we see from >>> + Linux side is a device which provides audio service by rpmsg channel. >>> + We can create different sound cards which access different hardwares >>> + such as SAI, MICFIL, .etc through building rpmsg channels between >>> + Cortex-A and Cortex-M. >>> >>> properties: >>> compatible: >>> @@ -85,6 +88,14 @@ properties: >>> This is a boolean property. If present, the receiving function >>> will be enabled. >>> >>> + fsl,platform: >>> + $ref: /schemas/types.yaml#/definitions/string >>> + description: | >>> + A string property to assign ASoC platform driver name. >> >> No, this is not a property of hardware. Naming of some drivers in some >> systems does not fit DTS and bindings. >> > > This property aims to tell the ASoC driver which rpmsg channel the > sound card depends on. If there are several sound cards sit on rpmsg, > we should pass correct information in dts node to specify the name of > rpmsg channel. That is why I meant to add this property. I just want to > use a string property to distinguish different names of rpmsg channel. > > Actually this property is hardware-related. As we discussed before, > this kind of sound card based on rpmsg works under this mechanism > Cortex-A core tells the Cortex-M core configuration of the PCM > parameters then Cortex-M controls real hardware devices. This property > specifying rpmsg channel represents the real hardware audio controller. > > That's my idea adding this property. Do you have any better suggestion? Any reason why not using phandle to sound card node? If your property is about rpmsg channel name, use something like that, e.g. "fsl,rpmsg-channel-name" or What you wrote in property description and here are quite different things... Best regards, Krzysztof
