From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
andriy.shevchenko@linux.intel.com, bparrot@ti.com,
andy.shevchenko@gmail.com, simon.budig@kernelconcepts.de,
hdegoede@redhat.com, fcooper@ti.com, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, kernel@pengutronix.de,
bcousson@baylibre.com, tony@atomide.com,
nicolas.ferre@microchip.com, ludovic.desroches@microchip.com,
s.hauer@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
shawnguo@kernel.org, mripard@kernel.org, wens@csie.org
Subject: Re: [PATCH 2/6] dt-bindings: Input: edt-ft5x06 - add disable wakeup-source documentation
Date: Wed, 2 Oct 2019 17:24:52 +0200 [thread overview]
Message-ID: <20191002152452.GN4106@piout.net> (raw)
In-Reply-To: <20191002130018.pvgipl6bkcv3dexj@pengutronix.de>
On 02/10/2019 15:00:18+0200, Marco Felsch wrote:
> Hi,
>
> all of you using a edt,* touchscreen and currently the driver marks
> the touchscreen as wakeup source. To keep backward compatibility I added
> a workaround binding (see below) but Dmitry prefer to use the normal
> "wakeup-source" binding and change the affected device-tree's
> (discussion below). Can you give me your ack/nack for Dmitry's solution?
>
Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Regards,
> Marco
>
> On 19-09-30 18:11, Rob Herring wrote:
> > On Tue, Sep 17, 2019 at 10:26:58AM -0700, Dmitry Torokhov wrote:
> > > On Tue, Sep 17, 2019 at 07:18:14PM +0200, Marco Felsch wrote:
> > > > Hi Dmitry,
> > > >
> > > > On 19-09-17 10:07, Dmitry Torokhov wrote:
> > > > > On Tue, Sep 17, 2019 at 05:58:04PM +0200, Marco Felsch wrote:
> > > > > > The default driver behaviour is to enable the wakeup-source everytime.
> > > > > > There are hardware designs which have a dedicated gpio to act as wakeup
> > > > > > device. So it must be allowed to disable the wakeup-source capability.
> > > > > >
> > > > > > This patch adds the binding documentation to disable the wakeup-source
> > > > > > capability.
> > > > > >
> > > > > > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> > > > > > ---
> > > > > > .../devicetree/bindings/input/touchscreen/edt-ft5x06.txt | 4 ++++
> > > > > > 1 file changed, 4 insertions(+)
> > > > > >
> > > > > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt
> > > > > > index 870b8c5cce9b..4d6524fe3cf4 100644
> > > > > > --- a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt
> > > > > > +++ b/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.txt
> > > > > > @@ -35,6 +35,10 @@ Optional properties:
> > > > > > - pinctrl-0: a phandle pointing to the pin settings for the
> > > > > > control gpios
> > > > > >
> > > > > > + - edt,disable-wakeup-source: If left the device will act as wakeup-source
> > > > > > + (for legacy compatibility). Add the property
> > > > > > + so the device won't act as wakeup-source.
> > > > >
> > > > > I think this is too ugly and I consider it being a bug in the driver
> > > > > that it enables wakeup unconditionally.
> > > >
> > > > That's right.
> > > >
> > > > > Let's just update DTS in tree for devices that actually want it (I am
> > > > > curious how many that do not declare "wakeup-source" have it working and
> > > > > actually want it) and key the dirver behavior off the standard property.
> > > >
> > > > There are a few DTS using this driver and the current driver behaviour.
> > > > We need to keep the backward compatibility since the DTB is part of the
> > > > firmware and firmware isn't always included during a system-update. I
> > > > know its ugly but IMHO that's the right way to go to keep the backward
> > > > compatibility. Let us see what the DT-folk says.
> > > >
> > > > > Until we start seeing this controller in devices that actually have DTS
> > > > > in hardware device tree I think it is better to use standard property.
> > > >
> > > > Sorry, I didn't get you here..
> > >
> > > What I was trying to say is that I have not actually seen DTB that is
> > > part of hardware or separately upgradable frimware (not talking about
> > > ppc or sparc boxes, but ones that might be using this driver). It is
> > > always built into the kernel in my experience, so backward compatibility
> > > is simply a tool that is being used to prevent us from being too wild
> > > with hacking on bindings, but rarely a practical concern.
> >
> > Well, that's self fulfilling...
> >
> > > In cases like this I think it is worthwhile to simply update in-tree
> > > DTS and arrive at a sane binding.
> >
> > Get the maintainers of the affected platforms to agree to the changes.
> >
> > Rob
> >
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-02 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190917155808.27818-1-m.felsch@pengutronix.de>
[not found] ` <20190917155808.27818-3-m.felsch@pengutronix.de>
[not found] ` <20190917170743.GO237523@dtor-ws>
[not found] ` <20190917171814.owcttekv56xgmsts@pengutronix.de>
[not found] ` <20190917172658.GQ237523@dtor-ws>
2019-09-30 23:11 ` [PATCH 2/6] dt-bindings: Input: edt-ft5x06 - add disable wakeup-source documentation Rob Herring
2019-10-02 13:00 ` Marco Felsch
2019-10-02 14:48 ` Maxime Ripard
2019-10-02 15:20 ` Benoit Parrot
2019-10-02 17:30 ` Dmitry Torokhov
2019-10-02 15:24 ` Alexandre Belloni [this message]
2019-10-14 9:14 ` Shawn Guo
[not found] ` <20190917155808.27818-6-m.felsch@pengutronix.de>
2019-09-30 23:12 ` [PATCH 5/6] dt-bindings: Input: edt-ft5x06 - add vdd supply documentation 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=20191002152452.GN4106@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcousson@baylibre.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fcooper@ti.com \
--cc=festevam@gmail.com \
--cc=hdegoede@redhat.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-input@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=m.felsch@pengutronix.de \
--cc=mripard@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=simon.budig@kernelconcepts.de \
--cc=tony@atomide.com \
--cc=wens@csie.org \
/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).