From: Krzysztof Kozlowski <krzk@kernel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Cathy Xu <ot_cathy.xu@mediatek.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>, Lei Xue <lei.xue@mediatek.com>,
wenbin.mei@mediatek.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Guodong Liu <guodong.liu@mediatek.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: mediatek: add support for mt8196
Date: Sat, 18 Jan 2025 10:13:06 +0100 [thread overview]
Message-ID: <76ab492e-ae9c-46eb-bf2e-d794863baf8d@kernel.org> (raw)
In-Reply-To: <66218a3c-04c5-42ea-ba9c-e0fbc72ed16f@collabora.com>
On 13/01/2025 14:20, AngeloGioacchino Del Regno wrote:
>>> +
>>> + properties:
>>> + pinmux:
>>> + description:
>>> + Integer array, represents gpio pin number and mux setting.
>>> + Supported pin number and mux varies for different SoCs, and are
>>> + defined as macros in dt-bindings/pinctrl/mt8196-pinfunc.h
>>> + directly, for this SoC.
>>> +
>>> + drive-strength:
>>> + enum: [2, 4, 6, 8, 10, 12, 14, 16]
>>> +
>>> + drive-strength-microamp:
>>> + enum: [125, 250, 500, 1000]
>>
>> Why duplicating properties? No, use only one.
>>
>
> The problem here is not entirely about duplicating properties, and I'm not
> sure that the reason is actually acceptable (but being this a special case
> the `description` field would be mandatory to have IMO!!).
>
> So, the reason for this separation is that the drive-strength-microamp does
> activate a special feature in the controller called "advanced drive strength
> mode", which is switching to different shunts that will decrease the power
> efficiency of the chip (by an ignorable amount, if that's one pin - but if
> that goes to something like 100 pins, it's not ignorable anymore).
>
> I'd be happy if we could let them retain both properties after putting a
> clear description of what's happening and why there are two of them.
It would be fine then, but please add some sort of description to these
fields documenting that difference.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-18 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 10:42 [PATCH v2 0/2] MediaTek pinctrl patch on mt8196 Cathy Xu
2025-01-10 10:42 ` [PATCH v2 1/2] dt-bindings: pinctrl: mediatek: add support for mt8196 Cathy Xu
2025-01-11 9:41 ` Krzysztof Kozlowski
2025-01-13 13:20 ` AngeloGioacchino Del Regno
2025-01-14 11:07 ` Cathy Xu (许华婷)
2025-01-18 9:13 ` Krzysztof Kozlowski [this message]
2025-01-14 11:01 ` Cathy Xu (许华婷)
2025-01-10 10:42 ` [PATCH v2 2/2] pinctrl: mediatek: add mt8196 driver Cathy Xu
2025-01-11 10:31 ` kernel test robot
2025-01-11 13:08 ` kernel test robot
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=76ab492e-ae9c-46eb-bf2e-d794863baf8d@kernel.org \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guodong.liu@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=lei.xue@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_cathy.xu@mediatek.com \
--cc=robh@kernel.org \
--cc=sean.wang@kernel.org \
--cc=wenbin.mei@mediatek.com \
/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