From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH] mc13xxx-ts: use zero as default value if no pdata was defined
Date: Tue, 20 Aug 2013 13:06:36 -0700 [thread overview]
Message-ID: <20130820200635.GA22769@core.coreip.homeip.net> (raw)
In-Reply-To: <20130820093432.GC26693@pengutronix.de>
On Tue, Aug 20, 2013 at 11:34:32AM +0200, Michael Grzeschik wrote:
> On Tue, Aug 20, 2013 at 03:34:33AM +0200, Samuel Ortiz wrote:
> > Hi Michael,
> >
> > On Tue, Aug 13, 2013 at 02:14:30PM +0200, Michael Grzeschik wrote:
> > > In case of devicetree, we currently don't have a way to append pdata for
> > > the touchscreen. The current approach is to bail out in that case.
> > > This patch makes it possible to probe the touchscreen without pdata
> > > and use zero as default values for the atox and ato adc conversion.
> > Would that still make the touchscreen somehow functional ?
>
> Yes, it still works. It just defaults to zero values in no pdata case.
>
> > If that's the case, and if Dmitry is fine with the ts part of this
> > patch, could you please separate the mfd part of this patch into a
> > separate one ?
>
> Why?
>
> The purpose of this patch is to have both cases working, pdata and no
> pdata.
My concern with allowing defaults with missing pdata or device tree data
is that it makes it easy for the integrator to miss the necessity of the
parameters and then start piling on driver workarounds. I have seen a
few examples of this happening, so I'd rather prefer an explicit values
if possible.
Thanks.
--
Dmitry
prev parent reply other threads:[~2013-08-20 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 12:14 [PATCH] mc13xxx-ts: use zero as default value if no pdata was defined Michael Grzeschik
2013-08-13 16:46 ` Dmitry Torokhov
2013-08-14 3:36 ` Michael Grzeschik
2013-08-20 1:34 ` Samuel Ortiz
2013-08-20 9:34 ` Michael Grzeschik
2013-08-20 9:50 ` Samuel Ortiz
2013-08-20 9:53 ` Michael Grzeschik
2013-08-20 20:06 ` Dmitry Torokhov [this message]
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=20130820200635.GA22769@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=mgr@pengutronix.de \
--cc=sameo@linux.intel.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 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).