mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Bryan Wu <cooloney@gmail.com>,
	Peter Meerwald <p.meerwald@bct-electronic.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Subject: [PATCH v4 0/5] PCA9633: Add support to PCA9634 and fix some problems
Date: Wed, 14 Aug 2013 09:14:21 +0200	[thread overview]
Message-ID: <1376464470-6845-1-git-send-email-ricardo.ribalda@gmail.com> (raw)


Add Support for the PCA9634 chip. Simimart to the 9633, but with 8 outputs instead of 4.
Fix bug when 2 chips where present on the system, the ledclass will fail and the chip wont probe.
Protect ledout register with a mutex to support updates of more than leds at the same time
Fix device tree parsing

v4: Rebase to latest leds-next and new patch to Fix the dt parsing

v3: Contains feedback from Bryan Wu
Bryan: Rename pca9633 to pca963x

v2: Contains feedback from Peter Meerwald
Peter: Fix typo on commit message. Add bus number to name

Ricardo Ribalda Delgado (4):
  leds-pca9633: Unique naming of the LEDs
  leds-pca9633: Add mutex to the ledout register
  leds-pca9633: Rename to leds-pca963x
  leds-pca963x: Fix device tree parsing

 drivers/leds/Kconfig                       |    2 +-
 drivers/leds/Makefile                      |    2 +-
 drivers/leds/leds-pca9633.c                |  435 --------------------------
 drivers/leds/leds-pca963x.c                |  460 ++++++++++++++++++++++++++++
 include/linux/platform_data/leds-pca9633.h |   41 ---
 include/linux/platform_data/leds-pca963x.h |   42 +++
 6 files changed, 504 insertions(+), 478 deletions(-)
 delete mode 100644 drivers/leds/leds-pca9633.c
 create mode 100644 drivers/leds/leds-pca963x.c
 delete mode 100644 include/linux/platform_data/leds-pca9633.h
 create mode 100644 include/linux/platform_data/leds-pca963x.h

-- 
1.7.10.4


             reply	other threads:[~2013-08-14  7:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  7:14 Ricardo Ribalda Delgado [this message]
2013-08-14  7:14 ` [PATCH v4 1/5] leds-pca9633: Add support for PCA9634 Ricardo Ribalda Delgado
2013-08-14 21:00   ` Bryan Wu
2013-08-14 21:05     ` Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 1/4] leds-pca9633: Unique naming of the LEDs Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 2/4] leds-pca9633: Add mutex to the ledout register Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 2/5] leds-pca9633: Unique naming of the LEDs Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 3/5] leds-pca9633: Add mutex to the ledout register Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 3/4] leds-pca9633: Rename to leds-pca963x Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 4/5] " Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 4/4] leds-pca963x: Fix device tree parsing Ricardo Ribalda Delgado
2013-08-14  7:14 ` [PATCH v4 5/5] " Ricardo Ribalda Delgado
2013-08-14 21:23 [PATCH v4 0/5] PCA9633: Add support to PCA9634 and fix some problems Ricardo Ribalda Delgado
2013-08-17  0:17 ` Bryan Wu

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=1376464470-6845-1-git-send-email-ricardo.ribalda@gmail.com \
    --to=ricardo.ribalda@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=p.meerwald@bct-electronic.com \
    --cc=rpurdie@rpsys.net \
    /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

all inboxes | Powered by JetHome®