From: Robin van der Gracht <robin@protonic.nl>
To: linux-kernel@vger.kernel.org
Cc: 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>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Jonathan Cameron <jic23@kernel.org>,
Mark Brown <broonie@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
devicetree@vger.kernel.org,
Robin van der Gracht <robin@protonic.nl>
Subject: [PATCH v5 0/2] auxdisplay: Introduce driver for ht16k33 LED controller
Date: Thu, 7 Apr 2016 10:53:59 +0200 [thread overview]
Message-ID: <cover.1460019147.git.robin@protonic.nl> (raw)
This patch series adds a driver for the ht16k33 LED controller and a
new vendor prefix for Holtek Semiconductor Inc.
Robin van der Gracht (2):
of: add vendor prefix for Holtek Semiconductor
auxdisplay: ht16k33: Driver for LED controller
.../devicetree/bindings/display/ht16k33.txt | 42 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/auxdisplay/Kconfig | 9 +
drivers/auxdisplay/Makefile | 1 +
drivers/auxdisplay/ht16k33.c | 563 +++++++++++++++++++++
5 files changed, 616 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/ht16k33.txt
create mode 100644 drivers/auxdisplay/ht16k33.c
--
2.5.0
next reply other threads:[~2016-04-07 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 8:53 Robin van der Gracht [this message]
2016-04-07 8:54 ` [PATCH v5 1/2] of: add vendor prefix for Holtek Semiconductor Robin van der Gracht
2016-04-11 14:44 ` Rob Herring
[not found] ` <cover.1460018947.git.robin@protonic.nl>
2016-04-07 8:54 ` [PATCH v5 2/2] auxdisplay: ht16k33: Driver for LED controller Robin van der Gracht
[not found] ` <e5324c8257d2ed8e464552a0900271a4f76bff9d.1460018947.git.robin-/Q/L1SwJa3aEVqv0pETR8A@public.gmane.org>
2016-04-11 14:49 ` Rob Herring
2016-04-11 14:49 ` Rob Herring
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=cover.1460019147.git.robin@protonic.nl \
--to=robin@protonic.nl \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=treding@nvidia.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.