From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Pavel Machek" <pavel@ucw.cz>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 09:29:10 +0000 [thread overview]
Message-ID: <20160121092909.GH5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160121091241.GS7192@pali>
The merge window is open, which is when development code that was merged
in good time prior to the merge window is sent upstream to Linus. Linux
maintainers may choose not to merge new code into their tree to avoid
disrupting the utility of linux-next until the merge window has closed.
linux-next is an integration tree to help find merge conflicts, it
exists to assist with the merge windows, not as a general test ground.
Thus, linux-next must only contain code for either the current open
merge window, or if the merge window is closed, the next merge window.
On Thu, Jan 21, 2016 at 10:12:41AM +0100, Pali Rohár wrote:
> On Saturday 26 December 2015 00:40:12 Pali Rohár wrote:
> > This patch adds adp1653 device into n900 DT structure. DT support in
> > adp1653 driver is there since v4.2-rc1 version.
> >
> > Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
> > ---
> > arch/arm/boot/dts/omap3-n900.dts | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
> > index 5f5e0f3..ba93642 100644
> > --- a/arch/arm/boot/dts/omap3-n900.dts
> > +++ b/arch/arm/boot/dts/omap3-n900.dts
> > @@ -522,6 +522,21 @@
> > amstaos,cover-comp-gain = <16>;
> > };
> >
> > + adp1653: led-controller@30 {
> > + compatible = "adi,adp1653";
> > + reg = <0x30>;
> > + enable-gpios = <&gpio3 24 GPIO_ACTIVE_HIGH>; /* 88 */
> > +
> > + flash {
> > + flash-timeout-us = <500000>;
> > + flash-max-microamp = <320000>;
> > + led-max-microamp = <50000>;
> > + };
> > + indicator {
> > + led-max-microamp = <17500>;
> > + };
> > + };
> > +
> > lp5523: lp5523@32 {
> > compatible = "national,lp5523";
> > reg = <0x32>;
>
> PING, who can take this patch?
>
> I still do not see it in linus tree nor in others like arm-soc...
>
> --
> Pali Rohár
> pali.rohar@gmail.com
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: "Pali Rohár" <pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Benoît Cousson"
<bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
"Tony Lindgren" <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
"Rob Herring" <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Pawel Moll" <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
"Mark Rutland" <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"Ian Campbell"
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
"Kumar Gala" <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"Pavel Machek" <pavel-+ZI9xUNit7I@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 09:29:10 +0000 [thread overview]
Message-ID: <20160121092909.GH5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160121091241.GS7192@pali>
The merge window is open, which is when development code that was merged
in good time prior to the merge window is sent upstream to Linus. Linux
maintainers may choose not to merge new code into their tree to avoid
disrupting the utility of linux-next until the merge window has closed.
linux-next is an integration tree to help find merge conflicts, it
exists to assist with the merge windows, not as a general test ground.
Thus, linux-next must only contain code for either the current open
merge window, or if the merge window is closed, the next merge window.
On Thu, Jan 21, 2016 at 10:12:41AM +0100, Pali Rohár wrote:
> On Saturday 26 December 2015 00:40:12 Pali Rohár wrote:
> > This patch adds adp1653 device into n900 DT structure. DT support in
> > adp1653 driver is there since v4.2-rc1 version.
> >
> > Signed-off-by: Pali Rohár <pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > ---
> > arch/arm/boot/dts/omap3-n900.dts | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
> > index 5f5e0f3..ba93642 100644
> > --- a/arch/arm/boot/dts/omap3-n900.dts
> > +++ b/arch/arm/boot/dts/omap3-n900.dts
> > @@ -522,6 +522,21 @@
> > amstaos,cover-comp-gain = <16>;
> > };
> >
> > + adp1653: led-controller@30 {
> > + compatible = "adi,adp1653";
> > + reg = <0x30>;
> > + enable-gpios = <&gpio3 24 GPIO_ACTIVE_HIGH>; /* 88 */
> > +
> > + flash {
> > + flash-timeout-us = <500000>;
> > + flash-max-microamp = <320000>;
> > + led-max-microamp = <50000>;
> > + };
> > + indicator {
> > + led-max-microamp = <17500>;
> > + };
> > + };
> > +
> > lp5523: lp5523@32 {
> > compatible = "national,lp5523";
> > reg = <0x32>;
>
> PING, who can take this patch?
>
> I still do not see it in linus tree nor in others like arm-soc...
>
> --
> Pali Rohár
> pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: n900: Include adp1653 device
Date: Thu, 21 Jan 2016 09:29:10 +0000 [thread overview]
Message-ID: <20160121092909.GH5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160121091241.GS7192@pali>
The merge window is open, which is when development code that was merged
in good time prior to the merge window is sent upstream to Linus. Linux
maintainers may choose not to merge new code into their tree to avoid
disrupting the utility of linux-next until the merge window has closed.
linux-next is an integration tree to help find merge conflicts, it
exists to assist with the merge windows, not as a general test ground.
Thus, linux-next must only contain code for either the current open
merge window, or if the merge window is closed, the next merge window.
On Thu, Jan 21, 2016 at 10:12:41AM +0100, Pali Roh?r wrote:
> On Saturday 26 December 2015 00:40:12 Pali Roh?r wrote:
> > This patch adds adp1653 device into n900 DT structure. DT support in
> > adp1653 driver is there since v4.2-rc1 version.
> >
> > Signed-off-by: Pali Roh?r <pali.rohar@gmail.com>
> > ---
> > arch/arm/boot/dts/omap3-n900.dts | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
> > index 5f5e0f3..ba93642 100644
> > --- a/arch/arm/boot/dts/omap3-n900.dts
> > +++ b/arch/arm/boot/dts/omap3-n900.dts
> > @@ -522,6 +522,21 @@
> > amstaos,cover-comp-gain = <16>;
> > };
> >
> > + adp1653: led-controller at 30 {
> > + compatible = "adi,adp1653";
> > + reg = <0x30>;
> > + enable-gpios = <&gpio3 24 GPIO_ACTIVE_HIGH>; /* 88 */
> > +
> > + flash {
> > + flash-timeout-us = <500000>;
> > + flash-max-microamp = <320000>;
> > + led-max-microamp = <50000>;
> > + };
> > + indicator {
> > + led-max-microamp = <17500>;
> > + };
> > + };
> > +
> > lp5523: lp5523 at 32 {
> > compatible = "national,lp5523";
> > reg = <0x32>;
>
> PING, who can take this patch?
>
> I still do not see it in linus tree nor in others like arm-soc...
>
> --
> Pali Roh?r
> pali.rohar at gmail.com
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-21 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 23:40 [PATCH] ARM: dts: n900: Include adp1653 device Pali Rohár
2015-12-25 23:40 ` Pali Rohár
2015-12-25 23:40 ` Pali Rohár
2015-12-26 18:35 ` Pavel Machek
2015-12-26 18:35 ` Pavel Machek
2016-01-09 22:38 ` Pali Rohár
2016-01-09 22:38 ` Pali Rohár
2016-01-09 22:38 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:12 ` Pali Rohár
2016-01-21 9:29 ` Russell King - ARM Linux [this message]
2016-01-21 9:29 ` Russell King - ARM Linux
2016-01-21 9:29 ` Russell King - ARM Linux
2016-01-21 9:50 ` Pali Rohár
2016-01-21 9:50 ` Pali Rohár
2016-01-21 10:03 ` Russell King - ARM Linux
2016-01-21 10:03 ` Russell King - ARM Linux
2016-01-21 10:18 ` Pavel Machek
2016-01-21 10:18 ` Pavel Machek
2016-01-21 10:18 ` Pavel Machek
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:38 ` Tony Lindgren
2016-01-21 16:54 ` Russell King - ARM Linux
2016-01-21 16:54 ` Russell King - ARM Linux
2016-01-27 10:02 ` Pali Rohár
2016-01-27 10:02 ` Pali Rohár
2016-01-27 11:18 ` Russell King - ARM Linux
2016-01-27 11:18 ` Russell King - ARM Linux
2016-01-27 16:24 ` Tony Lindgren
2016-01-27 16:24 ` Tony Lindgren
2016-01-27 16:24 ` Tony Lindgren
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=20160121092909.GH5783@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.