From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
jacopo mondi <jacopo@jmondi.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Lee Jones <lee.jones@linaro.org>,
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>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [RFC 2/4] sh: ecovec24: conditionally register backlight device
Date: Sat, 17 Mar 2018 17:33:35 +0000 [thread overview]
Message-ID: <20180317173335.GA183240@dtor-ws> (raw)
In-Reply-To: <20180317171631.GV1436@brightrain.aerifal.cx>
On Sat, Mar 17, 2018 at 01:16:31PM -0400, Rich Felker wrote:
> On Sat, Mar 17, 2018 at 07:21:17PM +0900, John Paul Adrian Glaubitz wrote:
> >
> >
> > > On Mar 17, 2018, at 6:25 PM, jacopo mondi <jacopo@jmondi.org> wrote:
> > >
> > > Hi Dmitry,
> > >
> > >> On Fri, Mar 16, 2018 at 04:38:00PM -0700, Dmitry Torokhov wrote:
> > >> Hi Jacopo,
> > >>
> > >>> On Fri, Mar 16, 2018 at 11:07:48AM +0100, jacopo mondi wrote:
> > >>> Hello Dmitry
> > >>>
> > >>> FYI I am brushing the ecovec board these days as well
> > >>> https://www.spinics.net/lists/linux-sh/msg52536.html
> > >>>
> > >>
> > >> What is the ecovec board BTW? Is it some devkit or what? It seems quite
> > >> old to me.
> > >
> > > Yes, it is a SuperH 4 based development board. It is old for sure. I'm
> > > also working on removing some stuff the ecovec board file is the only
> > > user of...
> >
> > Umh, but I’m still using the SH7724 Evovec board. Please don’t
> > remove support for that.
> >
> > The SuperH port of the Linux kernel is still maintained.
>
> Thanks. At some point it would be nice to remove the board file, but
> only once the conversion to device tree happens. If anyone has a list
> of boards that people are still using or have access to and who can do
> testing, it would be nice to compile that somewhere so we can figure
> out what needs to be tested and who can test it.
For me I simply want to remove the custom "pen down" handler for tsc2007
from ecovec24. Unfortunately it seems with the current code you have to
switch from interrupt delivery to GPIO access on the board and it is not
really compatible with common handler and ecovec24 is the only board
that needs this custom handler support. If we can remove it then we can
switch the driver to use generic device properties only.
Note that the driver is still functional without the pendown handler, it
uses alternative methods for detecting lifting the pen, but they are
less reliable. I wonder how many people use ecovec24 with the
touchscreen.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2018-03-17 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 22:41 [RFC 0/4] gpio-backlight: remove platform data support Dmitry Torokhov
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 [this message]
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=20180317173335.GA183240@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=dalias@libc.org \
--cc=daniel.thompson@linaro.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jacopo@jmondi.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).