[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SG2PR06MB336557EDAAE2950D192E40838BCBA@SG2PR06MB3365.apcprd06.prod.outlook.com>
Date: Wed, 4 Oct 2023 17:38:10 +0000
From: Billy Tsai <billy_tsai@...eedtech.com>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
CC: Jonathan Cameron <jic23@...nel.org>,
"lars@...afoo.de" <lars@...afoo.de>,
"joel@....id.au" <joel@....id.au>,
"andrew@...id.au" <andrew@...id.au>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Potin.Lai@...ntatw.com" <Potin.Lai@...ntatw.com>,
"patrickw3@...a.com" <patrickw3@...a.com>
Subject: Re: [PATCH v1] iio: adc: aspeed: Support deglitch feature.
> > > > Create event sysfs for applying the deglitch condition. When
> > > > in_voltageY_thresh_rising_en/in_voltageY_thresh_falling_en is set to true,
> > > > the driver will use the in_voltageY_thresh_rising_value and
> > > > in_voltageY_thresh_falling_value as threshold values. If the ADC value
> > > > falls outside this threshold, the driver will wait for the ADC sampling
> > > > period and perform an additional read once to achieve the deglitching
> > > > purpose.
> > > >
> > > > Signed-off-by: Billy Tsai <billy_tsai@...eedtech.com>
> >
> > > Hi Billy
> >
> > > This is pushing the meaning of the events interface too far.
> > > You can't use it to hide a value you don't like from userspace.
> >
> > > If you can explain what the condition is that you are seeing
> > > and what you need to prevent happening if it is seen that would help
> > > us figure out if there is another way to do this.
> >
> > > Jonathan
> >
> > Hi Jonathan,
> >
> > Currently, we are experiencing some voltage glitches while reading from our
> > controller, but we do not wish to report these false alarms to the user space.
> > Instead, we want to retry the operation as soon as possible. This is why the
> > driver requires this patch to handle retries internally, rather than relying on user
> > space which could introduce unpredictable timing for retrying the reading process.
> > This software approach aims to minimize the possibility of false alarms as much as possible.
> Thanks for the extra detail. Perhaps share more of that in the cover letter for v2.
Okay, I will incorporate more details into my commit message for v2.
> >
> > If you have any suggestions or recommendations regarding this situation, please feel free to
> > share them with me.
> Why do you need userspace control for the thresholds?
> Perhaps this is something that belongs in DT for a particular board design?
If the input voltage remains constant, these settings can be incorporated into the DTS properties for configuring the threshold. However, if the input voltage is subject to change, adding user-space control may offer more flexibility.
Thanks
Powered by blists - more mailing lists