From: <Andrei.Simion@microchip.com>
To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/6] regulator: mcp16502: Add supplier for regulators
Date: Thu, 8 Aug 2024 09:43:43 +0000 [thread overview]
Message-ID: <f078e908-b44b-4187-8e9d-a3d253cd352e@microchip.com> (raw)
In-Reply-To: <e0db4f2b-ce4f-4560-b586-1d8dbb75c7ff@sirena.org.uk>
On 02.08.2024 20:58, Mark Brown wrote:
>
> On Fri, Aug 02, 2024 at 02:25:15PM +0000, Andrei.Simion@microchip.com wrote:
>
>> In regulator.yaml exists .*-supply [1] which practically allows every
>> char sequence before -supply. In the binding microchip,mcp16502.yaml [2]
>> each node under the regulators includes all the rules/documentation
>> from regulator.yaml , so I supposed that it is unnecessary to add
>> in the binding of those new property.
>> What is your opinion? Let me know any thoughts.
> The specific names for a given device are supposed to be specified,
> there's a bunch of existing bindings that appear to do th
OK, I understand. Thank you for the clarification.
I will update the binding in patch set V2.
Also, I will update all the dts and dtsi files
according to the modification.
Best regards,
Andrei Simion
next prev parent reply other threads:[~2024-08-08 9:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 8:44 [PATCH 0/6] Add input voltage suppliers for PMIC MCP16502 regulators Andrei Simion
2024-08-02 8:44 ` [PATCH 1/6] regulator: mcp16502: Add supplier for regulators Andrei Simion
2024-08-02 12:56 ` Mark Brown
2024-08-02 14:25 ` Andrei.Simion
2024-08-02 17:58 ` Mark Brown
2024-08-05 12:43 ` Andrei.Simion
2024-08-07 7:35 ` Andrei.Simion
2024-08-08 9:43 ` Andrei.Simion [this message]
2024-08-08 11:52 ` Andrei.Simion
2024-08-02 8:44 ` [PATCH 2/6] ARM: dts: microchip: at91-sama7g5ek: Add reg_5v to supply PMIC nodes Andrei Simion
2024-08-02 8:44 ` [PATCH 3/6] ARM: dts: microchip: at91-sama7g54_curiosity: " Andrei Simion
2024-08-02 8:44 ` [PATCH 4/6] ARM: dts: microchip: at91-sama5d2_icp: " Andrei Simion
2024-08-02 8:44 ` [PATCH 5/6] ARM: dts: microchip: at91-sama5d27_wlsom1: " Andrei Simion
2024-08-02 8:44 ` [PATCH 6/6] ARM: dts: microchip: sama5d29_curiosity: " Andrei Simion
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=f078e908-b44b-4187-8e9d-a3d253cd352e@microchip.com \
--to=andrei.simion@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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