From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Simon Guinot <simon.guinot@sequanux.org>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>
Cc: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Dan Carpenter <dan.carpenter@oracle.com>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Vincent Donnefort <vdonnefort@gmail.com>
Subject: Re: [PATCH v2 0/3] Add DT support for netxbig LEDs
Date: Sat, 25 Jul 2015 21:36:22 +0200 [thread overview]
Message-ID: <55B3E536.5010107@gmail.com> (raw)
In-Reply-To: <55B3A32C.1010305@free-electrons.com>
Hi Gregory,
On 25.07.2015 16:54, Gregory CLEMENT wrote:
> Hi Simon, Bryan, Richard,
>
> On 18/06/2015 13:52, Simon Guinot wrote:
>> Hello,
>>
>> This patch series adds DT support for the LEDs found on the Kirkwood-based
>> LaCie boards 2Big and 5Big Network v2.
>
> I saw that some led related patch on kirkwood based board have been merged.
> What is the status of this series?
LED subsystem part has been merged to linux-next, since DTS files
are not required for the compilation to succeed. We've been waiting
for ARM/Marvell Kirkwood maintainer opinion to decide on how to proceed
regarding patch 2/4.
> I still have the patch 2 and 3 in my inbox waiting for being applied.
Patch 3 affects only drivers/leds/leds-ns2.c, you were probably
thinking of patch 1 which modifies the out of LED tree file
include/linux/platform_data/leds-kirkwood-ns2.h.
IMO it would be best if the whole series went through the
LED tree.
> Thanks,
>
> Gregory
>
>
>>
>> Changes since v1:
>> - Check timer mode value retrieved from DT.
>> - In netxbig_leds_get_of_pdata, don't use unsigned long variables to get
>> timer delay values from DT with function of_property_read_u32_index.
>> Instead, use a temporary u32 variable. This allows to silence a static
>> checker warning.
>> - Make timer property optional in the binding documentation. It is now
>> aligned with the driver code.
>>
>> Simon
>>
>> Simon Guinot (3):
>> leds: netxbig: add device tree binding
>> ARM: Kirkwood: add LED DT entries for netxbig boards
>> ARM: mvebu: remove static LED setup for netxbig boards
>>
>> .../devicetree/bindings/gpio/netxbig-gpio-ext.txt | 22 ++
>> .../devicetree/bindings/leds/leds-netxbig.txt | 92 ++++++++
>> arch/arm/boot/dts/kirkwood-net5big.dts | 60 +++++
>> arch/arm/boot/dts/kirkwood-netxbig.dtsi | 80 +++++++
>> arch/arm/mach-mvebu/Kconfig | 7 -
>> arch/arm/mach-mvebu/Makefile | 1 -
>> arch/arm/mach-mvebu/board.h | 21 --
>> arch/arm/mach-mvebu/kirkwood.c | 4 -
>> arch/arm/mach-mvebu/netxbig.c | 191 ----------------
>> drivers/leds/leds-netxbig.c | 250 +++++++++++++++++++--
>> include/dt-bindings/leds/leds-netxbig.h | 18 ++
>> 11 files changed, 501 insertions(+), 245 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/gpio/netxbig-gpio-ext.txt
>> create mode 100644 Documentation/devicetree/bindings/leds/leds-netxbig.txt
>> delete mode 100644 arch/arm/mach-mvebu/board.h
>> delete mode 100644 arch/arm/mach-mvebu/netxbig.c
>> create mode 100644 include/dt-bindings/leds/leds-netxbig.h
>>
>
>
--
Best Regards,
Jacek Anaszewski
next prev parent reply other threads:[~2015-07-25 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 11:52 [PATCH v2 0/3] Add DT support for netxbig LEDs Simon Guinot
2015-06-18 11:52 ` [PATCH v2 1/3] leds: netxbig: add device tree binding Simon Guinot
2015-06-18 11:52 ` [PATCH v2 2/3] ARM: Kirkwood: add LED DT entries for netxbig boards Simon Guinot
2015-06-29 12:45 ` Gregory CLEMENT
2015-06-18 11:52 ` [PATCH v2 3/3] ARM: mvebu: remove static LED setup " Simon Guinot
2015-06-29 12:45 ` Gregory CLEMENT
2015-07-25 14:54 ` [PATCH v2 0/3] Add DT support for netxbig LEDs Gregory CLEMENT
2015-07-25 19:36 ` Jacek Anaszewski [this message]
2015-07-25 20:45 ` Jacek Anaszewski
2015-07-28 10:30 ` Gregory CLEMENT
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=55B3E536.5010107@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=andrew@lunn.ch \
--cc=cooloney@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gregory.clement@free-electrons.com \
--cc=j.anaszewski@samsung.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=simon.guinot@sequanux.org \
--cc=vdonnefort@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;
as well as URLs for NNTP newsgroup(s).