From: Simon Arlott <simon@fire.lp0.eu>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
"Jacek Anaszewski" <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: leds-bcm6328: add more init configuration options
Date: Sun, 15 Nov 2015 17:27:44 +0000 [thread overview]
Message-ID: <5648C090.9060904@simon.arlott.org.uk> (raw)
commit 1d3ff22d633d35048c35c3deeead7ab116cebc32
Author: Álvaro Fernández Rojas <noltari@gmail.com>
Date: Thu Oct 8 12:35:55 2015 +0200
Documentation: leds: update DT bindings for leds-bcm6328
This patch adds latest DT bindings for leds-bcm6328 init register
configuration.
commit 9f82c778ce17789a038351a411ff65cd41033c7a
Author: Álvaro Fernández Rojas <noltari@gmail.com>
Date: Thu Oct 8 12:35:54 2015 +0200
leds-bcm6328: add more init configuration options
This patch adds more init register configuration options:
- Serial LEDs multiplexing.
- Serial LEDs clock signal low/high polarity.
- Serial LEDs data signal low/high polarity.
- Serial LEDs shift direction inverted/normal.
This was not a backwards-compatible change, because the driver is now
turning off all of the serial LED options by default when previously
it only turned off brcm,serial-leds and left the other options
unchanged.
There are currently no in-tree users of this binding, so any existing
users will be broken by this change.
--
Simon Arlott
next reply other threads:[~2015-11-15 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 17:27 Simon Arlott [this message]
2015-11-16 15:03 ` leds-bcm6328: add more init configuration options Jacek Anaszewski
[not found] ` <5649F040.6090002-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-11-16 21:35 ` Álvaro Fernández Rojas
2015-11-16 21:35 ` Álvaro Fernández Rojas
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=5648C090.9060904@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=noltari@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 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.