From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Lee Jones <lee.jones@linaro.org>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [RFC 0/4] gpio-backlight: remove platform data support
Date: Thu, 15 Mar 2018 22:41:58 +0000 [thread overview]
Message-ID: <20180315224202.96668-1-dmitry.torokhov@gmail.com> (raw)
Hi,
This series attempts to remove platform data support from gpio_blackllist
driver and switch it over to generic device properties/GPIO tables.
The only user of platform data was SuperH Ecovec24 board; please take a
look at patch #2 that tries to only register backlight when the board is
using LDC and not DVI.
Please note that I do not have the hardware (do we even care about
ecovec24? I'd like to rip out platform data support from tsc2007 as
well, but ecovec24 is using custom pendown handler and GPIOs have
to be switched off from interrupt mode to GPIO and back in that
pendown handler, which is all quite messy. If we do not care about
this board I'd much rather removed that custom pendown).
Thanks!
Dmitry Torokhov (4):
backlight: gpio_backlight: use generic device properties
sh: ecovec24: conditionally register backlight device
sh: ecovec24: convert backlight to use device properties
backlight: gpio_backlight: remove platform data support
arch/sh/boards/mach-ecovec24/setup.c | 47 ++++++----
drivers/video/backlight/gpio_backlight.c | 93 +++-----------------
include/linux/platform_data/gpio_backlight.h | 20 -----
3 files changed, 46 insertions(+), 114 deletions(-)
delete mode 100644 include/linux/platform_data/gpio_backlight.h
--
Dmitry
next reply other threads:[~2018-03-15 22:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 22:41 Dmitry Torokhov [this message]
2018-03-15 22:41 ` [RFC 1/4] backlight: gpio_backlight: use generic device properties Dmitry Torokhov
2018-03-27 11:53 ` Linus Walleij
2018-03-15 22:42 ` [RFC 2/4] sh: ecovec24: conditionally register backlight device Dmitry Torokhov
2018-03-16 10:07 ` jacopo mondi
2018-03-16 23:38 ` Dmitry Torokhov
2018-03-17 9:25 ` jacopo mondi
2018-03-17 10:21 ` John Paul Adrian Glaubitz
2018-03-17 17:16 ` Rich Felker
2018-03-17 17:33 ` Dmitry Torokhov
2018-03-17 17:55 ` John Paul Adrian Glaubitz
2018-03-18 10:54 ` jacopo mondi
2018-03-18 11:12 ` John Paul Adrian Glaubitz
2018-03-17 17:37 ` Dmitry Torokhov
2018-03-15 22:42 ` [RFC 3/4] sh: ecovec24: convert backlight to use device properties Dmitry Torokhov
2018-03-16 8:50 ` Geert Uytterhoeven
2018-03-16 23:40 ` Dmitry Torokhov
2018-03-16 10:08 ` jacopo mondi
2018-03-15 22:42 ` [RFC 4/4] backlight: gpio_backlight: remove platform data support Dmitry Torokhov
2018-03-27 11:55 ` Linus Walleij
2018-03-16 11:11 ` [RFC 0/4] gpio-backlight: " Daniel Thompson
2018-03-27 11:59 ` Linus Walleij
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=20180315224202.96668-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dalias@libc.org \
--cc=daniel.thompson@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).