From: Kartik Agarwala <agarwala.kartik@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] ASoC: dt-bindings: mt6358: Convert to dtschema
Date: Thu, 6 Jun 2024 19:49:04 +0530 [thread overview]
Message-ID: <c32b902e-0338-436b-85e1-827c48e0ee2b@gmail.com> (raw)
In-Reply-To: <c05f91f5-a878-4f36-b325-0ac8e038a7e5@linaro.org>
On 5/20/24 12:39 PM, Krzysztof Kozlowski wrote:
> On 18/05/2024 10:16, Kartik Agarwala wrote:
>> Convert Mediatek MT6358 Audio Codec bindings from text to dtschema.
>>
>> Signed-off-by: Kartik Agarwala <agarwala.kartik@gmail.com>
>> ---
>> .../bindings/sound/mediatek,mt6358.yaml | 47 +++++++++++++++++++
>> .../devicetree/bindings/sound/mt6358.txt | 26 ----------
>> 2 files changed, 47 insertions(+), 26 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/sound/mediatek,mt6358.yaml
>> delete mode 100644 Documentation/devicetree/bindings/sound/mt6358.txt
>>
>> diff --git a/Documentation/devicetree/bindings/sound/mediatek,mt6358.yaml b/Documentation/devicetree/bindings/sound/mediatek,mt6358.yaml
>> new file mode 100644
>> index 000000000..f57ef2aa5
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/sound/mediatek,mt6358.yaml
>> @@ -0,0 +1,47 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/sound/mediatek,mt6358.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Mediatek MT6358 Audio Codec
>> +
>> +maintainers:
>> + - Kartik Agarwala <agarwala.kartik@gmail.com>
>> +
>> +description: |
>
> Do not need '|' unless you need to preserve formatting.
>
>> + The communication between MT6358 and SoC is through Mediatek PMIC wrapper.
>> + For more detail, please visit Mediatek PMIC wrapper documentation.
>> + Must be a child node of PMIC wrapper.
>
> Did you update the PMIC wrapper binding with ref to this?
>
Hi Krzysztof,
I apologize incase this is something obvious but I am still not sure
if I understand what you expect here. Could you please explain this
a bit more? I thought that you wanted me to convert the Mediatek PMIC
wrapper but it already seems to be in DT-Schema format.[1]
[1]: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/soc/mediatek/mediatek%2Cpwrap.yaml
Thanks and Regards,
Kartik Agarwala
next prev parent reply other threads:[~2024-06-06 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 8:16 [PATCH] ASoC: dt-bindings: mt6358: Convert to dtschema Kartik Agarwala
2024-05-20 7:09 ` Krzysztof Kozlowski
2024-05-22 21:04 ` Kartik Agarwala
2024-05-23 6:04 ` Krzysztof Kozlowski
2024-06-06 14:19 ` Kartik Agarwala [this message]
2024-06-07 6:56 ` Krzysztof Kozlowski
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=c32b902e-0338-436b-85e1-827c48e0ee2b@gmail.com \
--to=agarwala.kartik@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
/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).