public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Rob Herring <robh@kernel.org>, Thierry Reding <thierry.reding@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: regulators: Document Tegra regulator coupling in json-schema
Date: Tue, 7 Dec 2021 00:55:18 +0300	[thread overview]
Message-ID: <dfb6b42c-16ed-ab17-b585-6b07d3d6874f@gmail.com> (raw)
In-Reply-To: <Ya51Ndf+VdRRdM9h@robh.at.kernel.org>

06.12.2021 23:40, Rob Herring пишет:
> On Mon, Dec 06, 2021 at 04:40:32PM +0100, Thierry Reding wrote:
>> From: Thierry Reding <treding@nvidia.com>
>>
>> Move the NVIDIA Tegra regulator coupling bindings from the free-form
>> text format into the existing json-schema file for regulators.
> 
> Do we need these properties for every single regulator? This should be 
> its own schema file and then referenced where it is needed.

These properties are SoC-specific, they describe how regulators are
integrated into SoC's power subsystem. Regulators themselves are
SoC-independent, i.e. PMIC's vendor and model don't matter for SoC.

  reply	other threads:[~2021-12-06 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 15:40 [PATCH] dt-bindings: regulators: Document Tegra regulator coupling in json-schema Thierry Reding
2021-12-06 15:52 ` Dmitry Osipenko
2021-12-06 20:40 ` Rob Herring
2021-12-06 21:55   ` Dmitry Osipenko [this message]
2021-12-07 15:25     ` Rob Herring
2021-12-07 15:49       ` Dmitry Osipenko

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=dfb6b42c-16ed-ab17-b585-6b07d3d6874f@gmail.com \
    --to=digetx@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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