From: "Clément Péron" <peron.clem@gmail.com>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Icenowy Zheng <icenowy@aosc.io>,
Jagan Teki <jagan@amarulasolutions.com>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v2 5/5] ARM: dts: sun50i: h6: Introduce Beelink GS1 board
Date: Fri, 5 Apr 2019 18:40:23 +0200 [thread overview]
Message-ID: <CAJiuCcdVsiKRxLFKnmAPnApi2EJANbuQf9WUESGE+LBP8zpD+A@mail.gmail.com> (raw)
In-Reply-To: <20190405151100.jjjg55z7sg35ijxw@flea>
Hi,
On Fri, 5 Apr 2019 at 17:11, Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> On Fri, Apr 05, 2019 at 02:53:35PM +0200, Clément Péron wrote:
> > Hi,
> >
> > Adding this r_pio regulators make a new error in the bootlog :
> >
> > [ 0.346843] sun50i-h6-r-pinctrl 7022000.pinctrl: Couldn't get bank
> > PL regulator
> > [ 0.346853] sun50i-h6-r-pinctrl 7022000.pinctrl: request() failed for pin 352
> > [ 0.346862] sun50i-h6-r-pinctrl 7022000.pinctrl: pin-352
> > (7081400.i2c) status -517
> > [ 0.346871] sun50i-h6-r-pinctrl 7022000.pinctrl: could not request
> > pin 352 (PL0) from group PL0 on device 7022000.pinctrl
> > [ 0.346878] mv64xxx_i2c 7081400.i2c: Error applying setting,
> > reverse things back
> >
> > PL0 and PL1 are SCK/SDA for the PMIC :(
>
> How was this DT tested then?
There was a mistake when I tested the patch v2 and only saw this after
posting the patch.
Can I submit a V3 without pio / r_pio regulators ? (+ the yaml patch separated)
Thanks,
>
> Maxime
>
> --
> Maxime Ripard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
next prev parent reply other threads:[~2019-04-05 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 12:24 [PATCH v2 1/5] arm64: allwinner: h6: orangepi: Add PIO regulators Clément Péron
2019-04-05 12:24 ` [PATCH v2 2/5] arm64: dts: allwinner: h6: pine64: " Clément Péron
2019-04-05 12:24 ` [PATCH v2 3/5] arm64: dts: allwinner: h6: move MMC pinctrl to dtsi Clément Péron
2019-04-05 12:24 ` [PATCH v2 4/5] dt-bindings: vendor-prefixes: add AZW Clément Péron
2019-04-05 12:42 ` Robin Murphy
2019-04-05 12:24 ` [PATCH v2 5/5] ARM: dts: sun50i: h6: Introduce Beelink GS1 board Clément Péron
2019-04-05 12:53 ` Clément Péron
2019-04-05 13:07 ` Clément Péron
[not found] ` <CAJiuCcfbnR+Jfj8Je_4HwgycCBEe92sx6zqwqgXpeiMe2jKL-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-05 15:11 ` Maxime Ripard
2019-04-05 16:40 ` Clément Péron [this message]
[not found] ` <20190405122446.2101-5-peron.clem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-05 15:10 ` Maxime Ripard
2019-04-05 15:08 ` [PATCH v2 1/5] arm64: allwinner: h6: orangepi: Add PIO regulators Maxime Ripard
2019-04-05 16:42 ` Clément Péron
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=CAJiuCcdVsiKRxLFKnmAPnApi2EJANbuQf9WUESGE+LBP8zpD+A@mail.gmail.com \
--to=peron.clem@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).