ADC device close and IRQ

2022-09-15 Thread TimH
I have sorted the touchscreen on the SAMA5D2 - minor errors in the init code "as supplied" meaning a couple of registers were not set up right. I have also found that priority inheritance is needed, at least for the ADC example app: I've not sat back or read my books to see why, but it works fo

Re: ADC device close and IRQ

2022-09-15 Thread Michal Lenc
Hi, > The easy option is to comment out the two calls, but I don't know if that' s > deemed acceptable, especially as other adc drivers do the same? I do not think this is correct since it is better to disable and detach the interrupt when we close the device. Instead I think the the e

RE: ADC device close and IRQ

2022-09-15 Thread TimH
Makes sense! I searched other drivers for where they called the detach but didn't think to see where those other drivers called the attach! Thanks :) >-Original Message- >From: Michal Lenc >Subject: Re: ADC device close and IRQ > >Hi, > >> The easy opt

RE: ADC device close and IRQ

2022-09-16 Thread TimH
t;Subject: RE: ADC device close and IRQ > >Makes sense! I searched other drivers for where they called the detach but >didn't think to see where those other drivers called the attach! > >Thanks :) > >>-Original Message- >>From: Michal Lenc >>Subject:

Re: ADC device close and IRQ

2022-09-16 Thread Nathan Hartman
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

RE: ADC device close and IRQ

2022-09-16 Thread TimH
>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 th

Re: ADC device close and IRQ

2022-09-16 Thread Nathan Hartman
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 l

RE: ADC device close and IRQ

2022-09-16 Thread TimH
>-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 d

Re: ADC device close and IRQ

2022-09-16 Thread Nathan Hartman
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

RE: ADC device close and IRQ

2022-10-24 Thread Tim Hardisty
artman >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 drive