From: marek.vasut@gmail•com (Marek Vasut)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] mx28: added LRADC and touchscreen support
Date: Mon, 23 Jan 2012 19:28:04 +0100 [thread overview]
Message-ID: <201201231928.05192.marek.vasut@gmail.com> (raw)
In-Reply-To: <4ED64650.4030402@prolan.hu>
> On 2011-11-29 20:09, Arnd Bergmann wrote:
> > On Sunday 27 November 2011, Jonathan Cameron wrote:
> >>> As indicated by Shawn, adding a new driver specific kernel-level ADC
> >>> interface is not a good idea. IIRC, the result of the last discussion
> >>> was that all ADC drivers should be part of IIO and you should use
> >>> the IIO in-kernel interfaces. Not sure what the state of that code
> >>> is, but if it's not in mainline yet, you should work with Jonathan
> >>> to make sure it gets there. Having more users for that code can
> >>> only speed up the process, and I'm going to refuse another ADC driver
> >>> in drivers/misc or arch/arm/mach-*/.
> >>
> >> Quick summary of IIO status. Nothing is in mainline yet. Intent is to
> >> get the first set of core code (including in kernel pull interfaces)
> >> into linux-next fairly shortly (these have had enough postive feedback
> >> now I think). Doing push interfaces (as I think we would need here) is
> >> possible with existing patches on top of the stuff in the iio staging
> >> tree but there are some 'interesting' cases where both push and pull
> >> interfaces exist that still need addressing.
> >>
> >> Also, note the push interface stuff (e.g. interrupt driven) requires a
> >> lot more of the IIO infrastructure to be in place (buffered support and
> >> the demux unit) so may still be some time. Personally my time is
> >> currently very restricted so all the help anyone can offer is most
> >> welcome!
> >
> > Ok, thanks for the summary!
> >
> > Peter, I guess what this means for you is that it's best to first
> > get your code working with the IIO/ADC stuff that is in staging,
> > and get the touchscreen driver ready for merging, on top of that.
> >
> > Ideally, you would also help out a bit on getting the IIO parts
> > you need graduated from staging. Given Jonathan's explanation,
> > I think my initial reaction was valid: we shouldn't take the
> > ADC driver outside of IIO, because that ends up being more painful
> > than getting the driver ready for inclusion now, and then rewriting
> > it shortly after.
> >
> > Arnd
>
> Thank you all for your comments. I'm now working on the interface
> change to iio, it may take some time...
> I've also applied most of the suggestions, they'll be in the next
> patches.
Are there any updates here?
M
prev parent reply other threads:[~2012-01-23 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 11:49 [PATCH] mx28: added LRADC and touchscreen support Peter Rusko
2011-11-24 12:59 ` Shawn Guo
2011-11-24 15:45 ` Peter Rusko
2011-11-24 22:59 ` Shawn Guo
2011-11-24 13:56 ` Lothar Waßmann
2011-11-24 14:44 ` Fabio Estevam
2011-11-24 15:01 ` Fabio Estevam
2011-11-24 21:10 ` Russell King - ARM Linux
2011-11-24 21:11 ` Russell King - ARM Linux
2011-11-25 16:02 ` Arnd Bergmann
2011-11-27 11:26 ` Jonathan Cameron
2011-11-29 19:09 ` Arnd Bergmann
2011-11-30 15:05 ` Peter Rusko
2012-01-23 18:28 ` Marek Vasut [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=201201231928.05192.marek.vasut@gmail.com \
--to=marek.vasut@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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