From: Juergen Beisert <jbe@pengutronix.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Marek Vasut <marex@denx.de>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: i.MX28 die temperature
Date: Wed, 27 Jun 2012 14:33:15 +0200 [thread overview]
Message-ID: <201206271433.15303.jbe@pengutronix.de> (raw)
In-Reply-To: <4FEAF75E.5090505@cam.ac.uk>
Hi Jonathan,
Jonathan Cameron wrote:
> [...]
> >>>>> [...]
> >>>>>
> >>>>>>> Take a look at:
> >>>>>>> http://www.spinics.net/lists/linux-iio/msg04345.html
> >>>>>>
> >>>>>> Any progress here with inclusion in some git tree?
> >>>>>
> >>>>> Well ... I recently raised from the dead. It's on the schedule,
> >>>>> obviously help is welcome.
> >>>>
> >>>> I tried a little bit with your driver. The disadvantage I see is, its
> >>>> claims all the free AD channels. But a few of them can also act as a
> >>>> touchscreen controller. Shouldn't be the driver handle the channel
> >>>> usage dynamically?
> >>>
> >>> I wonder, I'd rather see this driver behave as a composite driver, what
> >>> do you think?
> >>
> >> Alternative (though it's still in development) would be to use IIO
> >> as the ADC layer and sit the other parts on top.
> >
> > I think you need to adjust a few bits there and there in the hardware to
> > behave as a touchscreen. Will IIO be able to handle that somehow ?
>
> No means of doing it yet. I'm not entirely sure this can be done
> generically. I'm not really familiar enough with touchscreen adcs as
> none of my boards have one. At worst I'm sure we can put some
> hooks in to get hold of the underlying device if necessary.
It requires a more or less complex state-machine to switch the used 4 or 5
pins to different modes to measure the X/Y position and the pressure. And
these pins interfere with the ADC input pins.
> [...]
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
WARNING: multiple messages have this Message-ID (diff)
From: jbe@pengutronix.de (Juergen Beisert)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX28 die temperature
Date: Wed, 27 Jun 2012 14:33:15 +0200 [thread overview]
Message-ID: <201206271433.15303.jbe@pengutronix.de> (raw)
In-Reply-To: <4FEAF75E.5090505@cam.ac.uk>
Hi Jonathan,
Jonathan Cameron wrote:
> [...]
> >>>>> [...]
> >>>>>
> >>>>>>> Take a look at:
> >>>>>>> http://www.spinics.net/lists/linux-iio/msg04345.html
> >>>>>>
> >>>>>> Any progress here with inclusion in some git tree?
> >>>>>
> >>>>> Well ... I recently raised from the dead. It's on the schedule,
> >>>>> obviously help is welcome.
> >>>>
> >>>> I tried a little bit with your driver. The disadvantage I see is, its
> >>>> claims all the free AD channels. But a few of them can also act as a
> >>>> touchscreen controller. Shouldn't be the driver handle the channel
> >>>> usage dynamically?
> >>>
> >>> I wonder, I'd rather see this driver behave as a composite driver, what
> >>> do you think?
> >>
> >> Alternative (though it's still in development) would be to use IIO
> >> as the ADC layer and sit the other parts on top.
> >
> > I think you need to adjust a few bits there and there in the hardware to
> > behave as a touchscreen. Will IIO be able to handle that somehow ?
>
> No means of doing it yet. I'm not entirely sure this can be done
> generically. I'm not really familiar enough with touchscreen adcs as
> none of my boards have one. At worst I'm sure we can put some
> hooks in to get hold of the underlying device if necessary.
It requires a more or less complex state-machine to switch the used 4 or 5
pins to different modes to measure the X/Y position and the pressure. And
these pins interfere with the ADC input pins.
> [...]
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2012-06-27 12:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 15:13 i.MX28 die temperature Randle, Bill
2012-03-29 2:37 ` Shawn Guo
2012-03-29 15:52 ` Randle, Bill
2012-04-04 23:51 ` Marek Vasut
2012-04-05 0:07 ` Randle, Bill
2012-04-05 0:36 ` Fabio Estevam
2012-06-22 11:49 ` Juergen Beisert
2012-06-22 17:19 ` Marek Vasut
2012-06-26 8:12 ` Juergen Beisert
2012-06-26 19:02 ` Marek Vasut
2012-06-26 19:02 ` Marek Vasut
2012-06-27 7:21 ` Jonathan Cameron
2012-06-27 7:21 ` Jonathan Cameron
2012-06-27 12:00 ` Marek Vasut
2012-06-27 12:00 ` Marek Vasut
2012-06-27 12:06 ` Jonathan Cameron
2012-06-27 12:06 ` Jonathan Cameron
2012-06-27 12:25 ` Marek Vasut
2012-06-27 12:25 ` Marek Vasut
2012-06-27 12:33 ` Juergen Beisert [this message]
2012-06-27 12:33 ` Juergen Beisert
2012-06-27 22:58 ` Marek Vasut
2012-06-27 22:58 ` Marek Vasut
2012-06-28 8:00 ` Jonathan Cameron
2012-06-28 8:00 ` Jonathan Cameron
2012-06-28 3:05 ` Marek Vasut
2012-06-28 3:05 ` Marek Vasut
2012-06-28 15:42 ` Marek Vasut
2012-06-28 15:42 ` Marek Vasut
2012-10-23 8:48 ` Peter Turczak
2012-10-23 8:48 ` Peter Turczak
2012-10-23 8:52 ` Marek Vasut
2012-10-23 8:52 ` Marek Vasut
2012-10-23 10:22 ` Peter Turczak
2012-10-23 10:22 ` Peter Turczak
2012-10-23 10:32 ` Marek Vasut
2012-10-23 10:32 ` Marek Vasut
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=201206271433.15303.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.