[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <365485304.502411.1489612245583@email.1und1.de>
Date: Wed, 15 Mar 2017 22:10:45 +0100 (CET)
From: Stefan Wahren <stefan.wahren@...e.com>
To: Ksenija Stanojevic <ksenija.stanojevic@...il.com>
Cc: linux-input@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
pmeerw@...erw.net, jic23@...nel.org, linux-kernel@...r.kernel.org,
Dmitry Torokhov <dmitry.torokhov@...il.com>, knaack.h@....de,
lars@...afoo.de, harald@...ib.org, fabio.estevam@...escale.com,
linux-iio@...r.kernel.org, marex@...x.de
Subject: Re: [PATCH v14 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD
Hi Ksenija,
> Lee Jones <lee.jones@...aro.org> hat am 14. März 2017 um 12:05 geschrieben:
>
>
> On Wed, 01 Mar 2017, Dmitry Torokhov wrote:
>
> > On Wed, Mar 01, 2017 at 09:10:50PM +0100, Stefan Wahren wrote:
...
> > >
> > > Since touchscreen is optional it doesn't make to try to register it, notice in the touchscreen driver there is no touchscreen, give the user a confusing error and finally disable the clock.
> > >
> > > Here are my suggestions:
> > >
> > > 1) Use the solution from Patch V6 but with an explaining comment that touchscreen is optional
> > >
> > > if (!lradc->touchscreen_wire)
> > > return 0;
> > >
> > > 2) Return a special error from touchscreen registration so mfd knowns this result is expected.
> > >
> > > I'm open for better solutions.
> > >
> > > @Lee: What's your opinion?
> >
> > I am not Lee, but given that this module already parses touchscreen
> > properties and knows whether there is touchscreen or not, #1 seems
> > simple and logical.
>
> Sorry for the delay, I'm currently behind on my mail due to vacation
> and conferences.
>
> +1
>
could you please submit a V15? It would be great to get this into 4.12.
Thanks
Stefan
Powered by blists - more mailing lists