devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Vincent Pelletier <plr.vincent@gmail.com>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	qiuwenbo@kylinos.com.cn, devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Abdurachmanov <david.abdurachmanov@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v3 4/6] riscv: dts: sifive unmatched: Expose the FU740 core supply regulator
Date: Sun, 19 Dec 2021 16:14:23 -0600	[thread overview]
Message-ID: <CAL_JsqKWZL42A8G4y3J3uyC5n+Md70rnJjZz2Tt8eJkSPPuAPw@mail.gmail.com> (raw)
In-Reply-To: <5471232.RFuYXYORHR@diego>

On Sun, Dec 19, 2021 at 3:57 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Am Freitag, 17. Dezember 2021, 06:35:00 CET schrieb Palmer Dabbelt:
> > On Fri, 19 Nov 2021 14:55:40 PST (-0800), plr.vincent@gmail.com wrote:
> > > Provides monitoring of core voltage and current:
> > > tps544b20-i2c-0-1e
> > > Adapter: i2c-ocores
> > > vout1:       906.00 mV
> > > temp1:        -40.0°C  (high = +125.0°C, crit = +150.0°C)
> > > iout1:         5.06 A  (max = +20.00 A, crit max = +26.00 A)
> > >
> > > Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com>
> > >
> > > ---
> > > Note: checkpatch.pl complains about undocumented devicetree binding,
> > > which is fixed by:
> > >   https://lore.kernel.org/linux-devicetree/20211116110207.68494-1-krzysztof.kozlowski@canonical.com/T/#u
> > >
> > > Changes since v2:
> > > - Fix end-of-commit-message separator so change lists do not end up in them.
> > > Changes since v1:
> > > - Added missing "ti," prefix in compatible string.
> > > - Remove trailing "." on subject line.
> > > - Rename tree node.
> >
> > I see this in Rob's for-next as 761de79adc2c ("dt-bindings: hwmon: add
> > TI DC-DC converters"), so I'm going to hold off on this one until the
> > bindings land.
>
> Can't this patch then simply go into your for-next branch then?

Yes.

> The split is most times binding goes through the driver-tree
> (or Rob's dt tree) and the dts patch through an arch or soc tree.
>
> But in general once a maintainer accepts the binding it is ok
> to also apply the dts patch for the same cycle (aka merge window)
> the binding will be in.

Until there's issues with schema warnings showing up in specific
branches, going thru different trees isn't an issue. There's a lot of
warnings to fix first.

Rob

  reply	other threads:[~2021-12-19 22:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 22:55 [PATCH v3 1/6] riscv: dts: sifive unmatched: Name gpio lines Vincent Pelletier
2021-11-19 22:55 ` [PATCH v3 2/6] riscv: dts: sifive unmatched: Expose the board ID eeprom Vincent Pelletier
2021-11-21 17:23   ` Krzysztof Kozlowski
2021-11-19 22:55 ` [PATCH v3 3/6] riscv: dts: sifive unmatched: Expose the PMIC sub-functions Vincent Pelletier
2021-11-19 22:55 ` [PATCH v3 4/6] riscv: dts: sifive unmatched: Expose the FU740 core supply regulator Vincent Pelletier
2021-11-21 17:24   ` Krzysztof Kozlowski
2021-12-17  5:35   ` Palmer Dabbelt
2021-12-19 21:56     ` Heiko Stübner
2021-12-19 22:14       ` Rob Herring [this message]
2021-11-19 22:55 ` [PATCH v3 5/6] riscv: dts: sifive unmatched: Fix regulator for board rev3 Vincent Pelletier
2021-12-02 21:42   ` Palmer Dabbelt
2021-12-03  3:55     ` David Abdurachmanov
2021-11-19 22:55 ` [PATCH v3 6/6] riscv: dts: sifive unmatched: Link the tmp451 with its power supply Vincent Pelletier
2021-11-21 17:25   ` 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=CAL_JsqKWZL42A8G4y3J3uyC5n+Md70rnJjZz2Tt8eJkSPPuAPw@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=david.abdurachmanov@sifive.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=plr.vincent@gmail.com \
    --cc=qiuwenbo@kylinos.com.cn \
    /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).