[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb34e446-2904-a357-e54b-3e82a2b0745c@linaro.org>
Date: Fri, 9 Dec 2022 15:56:24 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Trevor Wu (吳文良) <Trevor.Wu@...iatek.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"broonie@...nel.org" <broonie@...nel.org>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
"tiwai@...e.com" <tiwai@...e.com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"perex@...ex.cz" <perex@...ex.cz>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v3 10/12] dt-bindings: mediatek: mt8188: add audio afe
document
On 09/12/2022 11:56, Trevor Wu (吳文良) wrote:
>>> +
>>> +patternProperties:
>>> + "^mediatek,etdm-in[1-2]-chn-disabled$":
>>> + $ref: /schemas/types.yaml#/definitions/uint8-array
>>> + minItems: 1
>>> + maxItems: 16
>>> + description:
>>> + By default, all data received from ETDM pins will be
>>> outputed to
>>> + memory. etdm in supports disable_out in direct mode(w/o
>>> interconn).
>>> + User can specify the channel ID which they hope dropping and
>>> then
>>> + the specified channel won't be seen on memory.
>>
>> So we know what are the IDs but it's a mystery what are the values.
>> Especially with unique values - how any of these should case that
>> channel "won't be seen in memory"?
>>
> For example,
> FE can support 14ch, but BE(etdm) can't support 14ch(it can support
> 16ch).
> In the case, we can configure 16ch to etdm and make use of the property
> to disable the last two channels.
>
> mediatek,etdm-in1-chn-disabled = /bits/ 8 <0xE 0xF>;
Your description should explain that this is a list of channel IDs which
should be disabled.
>
>
>>> + uniqueItems: true
>>> + items:
>>> + minimum: 0
>>> + maximum: 15
>>> +
>>> + "^mediatek,etdm-in[1-2]-mclk-always-on-rate-hz$":
>>> + description: Specify etdm in mclk output rate for always on
>>> case.
>>
>> How is it different than assigned-clock-rates?
>>
> This includes clock enabling at init stage.
assigned-clock-rates are also at init stage. I asked what is different.
>
>>> +
>>> + "^mediatek,etdm-out[1-3]-mclk-always-on-rate-hz$":
>>> + description: Specify etdm out mclk output rate for always on
>>> case.
>>> +
>>> + "^mediatek,etdm-in[1-2]-multi-pin-mode$":
>>> + type: boolean
>>> + description: if present, the etdm data mode is I2S.
>>> +
>>> + "^mediatek,etdm-out[1-3]-multi-pin-mode$":
>>> + type: boolean
>>> + description: if present, the etdm data mode is I2S.
>>> +
>>> + "^mediatek,etdm-in[1-2]-cowork-source$":
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description:
>>> + etdm modules can share the same external clock pin. Specify
>>> + which etdm clock source is required by this etdm in moudule.
>>
>> typo: module
>>
Best regards,
Krzysztof
Powered by blists - more mailing lists