Actually a little more complicated as the detach and disable in adc close then
kills the touch screen driver as well (it uses the ADC). l'll figure out a way,
I'm sure!
>-Original Message-
>From: TimH
>Sent: 15 September 2022 18:48
>To: dev@nuttx.apache.org
>Subject: RE: ADC device clos
On Fri, Sep 16, 2022 at 7:20 AM TimH wrote:
> Actually a little more complicated as the detach and disable in adc close
> then kills the touch screen driver as well (it uses the ADC). l'll figure
> out a way, I'm sure!
I haven't looked at the code, but it sounds like any driver being closed
sh
>From: Nathan Hartman
>Sent: 16 September 2022 12:31
>To: dev@nuttx.apache.org
>Subject: Re: ADC device close and IRQ
>
>On Fri, Sep 16, 2022 at 7:20 AM TimH wrote:
>
>> Actually a little more complicated as the detach and disable in adc
>> close then kills the touch screen driver as well (it use
On Fri, Sep 16, 2022 at 7:33 AM TimH wrote:
> >From: Nathan Hartman
> >Sent: 16 September 2022 12:31
> >To: dev@nuttx.apache.org
> >Subject: Re: ADC device close and IRQ
> >
> >On Fri, Sep 16, 2022 at 7:20 AM TimH wrote:
> >
> >> Actually a little more complicated as the detach and disable in a
>-Original Message-
>From: Nathan Hartman
>Sent: 16 September 2022 12:37
>
>On Fri, Sep 16, 2022 at 7:33 AM TimH wrote:
>
>> >From: Nathan Hartman
>> >Sent: 16 September 2022 12:31
>> >To: dev@nuttx.apache.org
>> >Subject: Re: ADC device close and IRQ
>> >
>> >On Fri, Sep 16, 2022 at 7:2
On Fri, Sep 16, 2022 at 7:44 AM TimH wrote:
> >> At present (by default/out of the box) there are two drivers - one for
> >> the TS, registered as /dev/input0, the other for the ADC, as
> >> /dev/adc0. There are, indeed, counts for each separate driver, but no
> >"cross-coupling".
> >>
> >> Perhap
