From: Krzysztof Kozlowski <krzk@kernel.org>
To: Macpaul Lin <macpaul.lin@mediatek.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sen Chu <sen.chu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org,
netdev@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-sound@vger.kernel.org,
Alexandre Mergnat <amergnat@baylibre.com>,
Bear Wang <bear.wang@mediatek.com>,
Pablo Sun <pablo.sun@mediatek.com>,
Macpaul Lin <macpaul@gmail.com>,
Chris-qj chen <chris-qj.chen@mediatek.com>,
MediaTek Chromebook Upstream
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH v7 3/3] dt-bindings: mfd: mediatek: mt6397: Convert to DT schema format
Date: Tue, 1 Oct 2024 08:35:58 +0200 [thread overview]
Message-ID: <5a29ddaf-cc01-498c-943c-b65736e2899e@kernel.org> (raw)
In-Reply-To: <psjwbo2vecr54vmz5ib2eurhpcaynpc67rc2nwuj2gtej6gqiu@4ysahn2ghthf>
On 01/10/2024 08:29, Krzysztof Kozlowski wrote:
> On Mon, Sep 30, 2024 at 03:33:11PM +0800, Macpaul Lin wrote:
>> Convert the mfd: mediatek: mt6397 binding to DT schema format.
>>
>> MT6323, MT6358, and MT6397 are PMIC devices with multiple function
>> subdevices. They share a common PMIC design but have variations in
>> subdevice combinations.
>>
>> Key updates in this conversion:
>>
>> 1. RTC:
>> - Convert rtc-mt6397.txt and merge into parent MT6397 PMIC DT schema.
>>
>> 2. Regulators:
>> - Align to generic name "regulators".
>> - Update references from .txt to .yaml for mt6323, mt6358, and mt6397
>> regulators.
>> - Simplify regulator name labels in device tree examples.
>> - Add a new 'mt6359-regulator' to the compatibles of regulators.
>
> Why?
>
>> Merge from the other patch [1].
>>
>> 3. ADC:
>> - Add a new 'adc' property and include a $ref for sub-device node of
>> MT6359 PMIC AUXADC: 'mediatek,mt6359-auxadc'.
>> Merge from the other patch [1].
>>
>> 4. Audio Codec:
>> - Simplify Audio Codec part with updating compatible items.
>> - Add 'mt6359-codec' to the compatible
>
> Why?
> .
>>
>> 5. Clocks:
>> - Align to generic name "clocks" for clockbuffer subdevices.
>>
>> 6. LEDs:
>> - Convert leds-mt6323.txt and merge into parent MT6397 PMIC DT schema.
>> - Update LED binding.
>>
>> 7. Keys:
>> - Add detailed descriptions for power and home keys.
>> - Add compatible: mediatek,mt6358-keys.
>>
>> 8. Power Controller:
>> - Convert mt6323-poweroff.txt and merge into parent MT6397 PMIC DT
>> schema.
>> - Add #power-domain-cells property to fix dt-binding check error.
>> - Clarify "BBPU" as "Baseband power up".
>>
>> 9. Pinctrl:
>> - Align to generic name "pinctrl" instead of "pin-controller".
>>
>> 10. Compatible:
>> - Drop "mediatek,mt6357" since there is a separated DT Schema
>> for PMIC MT6357.
>>
>> 11. Examples:
>> - MT6323: Retain complete examples for this PMIC.
>> - MT6358 and MT6397: simplify settings in regulators.
>> - Preserve "audio-codec", "clocks", "pinctrl", "rtc", and "keys"
>> sections as they contain typical settings for different PMICs.
>>
>> Additional updates:
>> - MAINTAINERS: Add co-maintainers and reference to
>> mfd/mediatek,mt6397.yaml for LED and power-controller drivers.
>> - input/mediatek,pmic-keys.yaml: Update reference to
>> mfd/mediatek,mt6397.yaml.
>>
>> References:
>> [1] https://lore.kernel.org/all/20240925171156.9115-1-macpaul.lin@mediatek.com/
>>
>> Signed-off-by: Sen Chu <sen.chu@mediatek.com>
>> Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>
>> ---
>
>> +
>> + adc:
>> + type: object
>> + $ref: /schemas/iio/adc/mediatek,mt6359-auxadc.yaml#
>> + unevaluatedProperties: false
>> +
>> + audio-codec:
>> + type: object
>> + description:
>> + Audio codec support with MT6358, MT6359, and MT6397.
>> + additionalProperties: true
>
> No, this cannot be true. Schema is incomplete for listed compatibles.
I saw now your patch for ASoC, so this is fine.
All my other questions stay valid - why are you adding new devices in
patch which is supposed to be ONLY conversion.
>
>> +
>> + properties:
>> + compatible:
>> + oneOf:
>> + - enum:
>> + - mediatek,mt6358-sound
>> + - mediatek,mt6359-codec
>
> There was no such compatible.
>
> Why do you add non-existing compatibles during conversion?
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-01 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 7:33 [PATCH v7 1/3] regulator: dt-bindings: mt6323: Convert to DT schema Macpaul Lin
2024-09-30 7:33 ` [PATCH v7 2/3] ASoC: dt-bindings: mt6358: Convert to DT Schema Macpaul Lin
2024-10-01 6:34 ` Krzysztof Kozlowski
2024-10-01 7:05 ` Macpaul Lin
2024-10-01 7:50 ` Macpaul Lin
2024-10-01 9:19 ` Krzysztof Kozlowski
2024-10-01 8:56 ` Krzysztof Kozlowski
2024-09-30 7:33 ` [PATCH v7 3/3] dt-bindings: mfd: mediatek: mt6397: Convert to DT schema format Macpaul Lin
2024-10-01 6:29 ` Krzysztof Kozlowski
2024-10-01 6:35 ` Krzysztof Kozlowski [this message]
2024-10-01 7:56 ` Macpaul Lin
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=5a29ddaf-cc01-498c-943c-b65736e2899e@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=alexandre.belloni@bootlin.com \
--cc=amergnat@baylibre.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bear.wang@mediatek.com \
--cc=broonie@kernel.org \
--cc=chris-qj.chen@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--cc=macpaul@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pablo.sun@mediatek.com \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sen.chu@mediatek.com \
--cc=sre@kernel.org \
--cc=wenst@chromium.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).