From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 41CB2CDB474 for ; Tue, 17 Oct 2023 19:16:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=kQ3D/pRuLg5ihFN07n+VdBhJwNXyQT90EzBc6f2fPBI=; b=dYJCzgPOTKPoCv 30vGXLBL035Td+SrZWgeuwgS4j1pr1SyzM+SwielOb0BeNAgygzpg0vQi7wI5mlSQRuZm7PHLi+fX /gPgJjGt2bgwH0QmnOdyM64R1hE4V9+v+jDY+Ph5HCXC0DTiOMVZLgdFPmcxmTzOv1VeDxB634RZT WCQmTUXpLR+0qKHyuqM7XM6e2/hUE1CL7k88vhECxreVbwSKBaR/2YRBzpacOG6WLAj4ckRvRZmmk +SyvFQYQZ/tbvntAV04Q3raj8oa/OouUVPTg5DSa+5CYluWfN/B/2P6txXKpcXxAdFf5c8EBM47fE Ch6KP3Jp5JaqvVgM9AyA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qspXI-00D45U-2B; Tue, 17 Oct 2023 19:15:24 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qspXE-00D44g-2D for linux-arm-kernel@lists.infradead.org; Tue, 17 Oct 2023 19:15:22 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 9B987CE20E5; Tue, 17 Oct 2023 19:15:16 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 67603C433CB; Tue, 17 Oct 2023 19:15:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697570115; bh=1FH2NiT0/UIAW9o7PfkE2WEJ0KQQ/92RAQnCv8fQwU4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GP6aDR68d48jUNYRKmDRMWXr5sPPdyOqLEW+eRRXOP4EspT4tJvRHdvqYo2a05LKk w83cFu2uDn+3f3MiB3xgZT6fJEmbYr38RksEcy8/MPlYbQ2k91pdLYWNChkMr55KaV RAVBci/zZS7ToXiZh5Ydphq0gsKZDxXvnnEr3Byg/HNoQeQ4ZrPxegnwcP+kAbSybZ a8rtWGQivfZ6h0lc1H8Mih40VDdqxkaW36nT+g69xcVD7qZAEVlHOd77Q8czePIIju GCR6AJvfasZijj2KwMpZ4SCfTJ0W16yZtjefzYc+CsxKdTfWPHci5zTHw718OCaICl uTVnaRiLHbjig== Date: Tue, 17 Oct 2023 20:15:33 +0100 From: Jonathan Cameron To: Billy Tsai Cc: Jonathan Cameron , "lars@metafoo.de" , "joel@jms.id.au" , "andrew@aj.id.au" , "linux-iio@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org, Potin.Lai@quantatw.com, patrickw3@meta.com Subject: Re: [PATCH v1] iio: adc: aspeed: Support deglitch feature. Message-ID: <20231017201346.2f4f6b01@jic23-huawei> In-Reply-To: References: <20230925081845.4147424-1-billy_tsai@aspeedtech.com> <20230930174501.039095da@jic23-huawei> <20231002103940.00001dbd@Huawei.com> <20231005150753.38e79c20@jic23-huawei> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231017_121521_091592_E16FDD4D X-CRM114-Status: GOOD ( 37.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 17 Oct 2023 11:10:54 +0000 Billy Tsai wrote: > > > > > > > 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 > > > > > > > > > > > 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. > > > My concern is that it's an interface userspace probably won't know how to use, or > > will misuse given this seems to be papering over bad hardware. > > > If there is a 'safe' value to put in DT I'd prefer to see that. I guess it might be per > > channel thing to adjust for different expected voltage ranges? > > Yes, the voltage ranges should be adjusted based on each individual channel. > I'm not entirely sure what you mean by the term 'safe' value. > Are you suggesting that a DTS property should be used to constrain the threshold ranges? Or someting else? > From my point of view, I think misusing this feature will only increase the sampling period of the ADC values and decrease the sensitivity. > As the name of this feature , it is primarily used to eliminate or mitigate glitches in readings. > Note a good choice of wording from me. I meant, for a given design (and hence DTS) is there a reasonable value that will work for all instances of that design? If there is it is a characteristic of the board design and should be in DT. If there isn't, how do you calibrate it for individual devices? Jonathan > Thanks > > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel