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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1B8B7C433FE for ; Sun, 9 Jan 2022 15:38:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233962AbiAIPiR convert rfc822-to-8bit (ORCPT ); Sun, 9 Jan 2022 10:38:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231642AbiAIPiQ (ORCPT ); Sun, 9 Jan 2022 10:38:16 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 70EBBC06173F; Sun, 9 Jan 2022 07:38:15 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 1A468B80C72; Sun, 9 Jan 2022 15:38:14 +0000 (UTC) Received: from jic23-huawei (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.kernel.org (Postfix) with ESMTPSA id BC791C36AEB; Sun, 9 Jan 2022 15:38:09 +0000 (UTC) Date: Sun, 9 Jan 2022 15:44:04 +0000 From: Jonathan Cameron To: Oleksij Rempel Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Pengutronix Kernel Team , David Jander , Robin van der Gracht , linux-iio@vger.kernel.org, Lars-Peter Clausen Subject: Re: [PATCH v1 1/1] iio: adc: tsc2046: rework the trigger state machine Message-ID: <20220109154404.75e0ed2f@jic23-huawei> In-Reply-To: <20220107074017.2762347-1-o.rempel@pengutronix.de> References: <20220107074017.2762347-1-o.rempel@pengutronix.de> X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 7 Jan 2022 08:40:17 +0100 Oleksij Rempel wrote: > Initially this was designed to: > | Fix sleeping in atomic context warning and a deadlock after iio_trigger_poll() > | call > | > | If iio_trigger_poll() is called after IRQ was disabled, we will call > | reenable_trigger() directly from hard IRQ or hrtimer context instead of > | IRQ thread. In this case we will run in to multiple issue as sleeping in atomic > | context and a deadlock. > | > | To avoid this issue, rework the trigger to use state machine. All state > | changes are done over the hrtimer, so it allows us to drop fsleep() and > | avoid the deadlock. > > This issue was fixed by: 9020ef659885 ("iio: trigger: Fix a scheduling > whilst atomic issue seen on tsc2046"). > > Even if the root cause of this issue probably will and can be fixed in the iio > core, this patch can be seen as clean-up to provide better internal state > machine. Probably want to update this text? A few comments below. > > Fixes: 9374e8f5a38d ("iio: adc: add ADC driver for the TI TSC2046 controller") From above isn't this now fixed? The cleanup here is just making things easier to follow I think... > Signed-off-by: Oleksij Rempel > --- > drivers/iio/adc/ti-tsc2046.c | 102 ++++++++++++++++++++--------------- > 1 file changed, 58 insertions(+), 44 deletions(-) > > diff --git a/drivers/iio/adc/ti-tsc2046.c b/drivers/iio/adc/ti-tsc2046.c > index d84ae6b008c1..91f6bd5effe7 100644 > --- a/drivers/iio/adc/ti-tsc2046.c > +++ b/drivers/iio/adc/ti-tsc2046.c > @@ -123,14 +123,21 @@ struct tsc2046_adc_ch_cfg { > unsigned int oversampling_ratio; > }; > > +enum tsc2046_state { > + TSC2046_STATE_STANDBY, > + TSC2046_STATE_ENABLE_IRQ_POLL, > + TSC2046_STATE_POLL, > + TSC2046_STATE_ENABLE_IRQ, > +}; > + > struct tsc2046_adc_priv { > struct spi_device *spi; > const struct tsc2046_adc_dcfg *dcfg; > > struct iio_trigger *trig; > struct hrtimer trig_timer; > - spinlock_t trig_lock; > - unsigned int trig_more_count; > + enum tsc2046_state state; > + spinlock_t state_lock; > > struct spi_transfer xfer; > struct spi_message msg; > @@ -411,21 +418,47 @@ static const struct iio_info tsc2046_adc_info = { > .update_scan_mode = tsc2046_adc_update_scan_mode, > }; > > -static enum hrtimer_restart tsc2046_adc_trig_more(struct hrtimer *hrtimer) > +static enum hrtimer_restart tsc2046_adc_timer(struct hrtimer *hrtimer) > { > struct tsc2046_adc_priv *priv = container_of(hrtimer, > struct tsc2046_adc_priv, > trig_timer); > unsigned long flags; > > - spin_lock_irqsave(&priv->trig_lock, flags); > - > - disable_irq_nosync(priv->spi->irq); > - > - priv->trig_more_count++; > - iio_trigger_poll(priv->trig); > - > - spin_unlock_irqrestore(&priv->trig_lock, flags); > + spin_lock_irqsave(&priv->state_lock, flags); > + switch (priv->state) { > + case TSC2046_STATE_ENABLE_IRQ_POLL: > + /* > + * IRQ handler called iio_trigger_poll() to sample ADC. > + * Here we > + * - re-enable IRQs > + * - start hrtimer for timeout if no IRQ will occur > + */ > + priv->state = TSC2046_STATE_POLL; > + enable_irq(priv->spi->irq); I comment on this below, but I'm not sure why you don't move the enable_irq() here out of this timer function and then have the first entry of the timer go directly to TSC2046_STATE_POLL after a longer initial wait. It's been a long time since I looked at this, so perhaps I'm missing the point. What you have here works as far as I can see, it just seems to push more than necessary into the state machine. > + hrtimer_start(&priv->trig_timer, > + ns_to_ktime(priv->scan_interval_us * > + NSEC_PER_USEC), > + HRTIMER_MODE_REL_SOFT); > + break; > + case TSC2046_STATE_POLL: > + disable_irq_nosync(priv->spi->irq); > + priv->state = TSC2046_STATE_ENABLE_IRQ; > + /* iio_trigger_poll() starts hrtimer */ > + iio_trigger_poll(priv->trig); > + break; > + case TSC2046_STATE_ENABLE_IRQ: > + priv->state = TSC2046_STATE_STANDBY; > + enable_irq(priv->spi->irq); > + break; > + case TSC2046_STATE_STANDBY: > + fallthrough; > + default: > + dev_warn(&priv->spi->dev, "Got unexpected state: %i\n", > + priv->state); > + break; > + } > + spin_unlock_irqrestore(&priv->state_lock, flags); > > return HRTIMER_NORESTART; > } > @@ -434,16 +467,17 @@ static irqreturn_t tsc2046_adc_irq(int irq, void *dev_id) > { > struct iio_dev *indio_dev = dev_id; > struct tsc2046_adc_priv *priv = iio_priv(indio_dev); > - > - spin_lock(&priv->trig_lock); > + unsigned long flags; > > hrtimer_try_to_cancel(&priv->trig_timer); > > - priv->trig_more_count = 0; > + spin_lock_irqsave(&priv->state_lock, flags);x` > disable_irq_nosync(priv->spi->irq); > - iio_trigger_poll(priv->trig); > + priv->state = TSC2046_STATE_ENABLE_IRQ_POLL; > > - spin_unlock(&priv->trig_lock); > + /* iio_trigger_poll() starts hrtimer */ > + iio_trigger_poll(priv->trig); > + spin_unlock_irqrestore(&priv->state_lock, flags); > > return IRQ_HANDLED; > } > @@ -452,37 +486,16 @@ static void tsc2046_adc_reenable_trigger(struct iio_trigger *trig) > { > struct iio_dev *indio_dev = iio_trigger_get_drvdata(trig); > struct tsc2046_adc_priv *priv = iio_priv(indio_dev); > - unsigned long flags; > - int delta; > + ktime_t tim; > > /* > * We can sample it as fast as we can, but usually we do not need so > * many samples. Reduce the sample rate for default (touchscreen) use > * case. > - * Currently we do not need a highly precise sample rate. It is enough > - * to have calculated numbers. > - */ > - delta = priv->scan_interval_us - priv->time_per_scan_us; > - if (delta > 0) > - fsleep(delta); > - > - spin_lock_irqsave(&priv->trig_lock, flags); > - > - /* > - * We need to trigger at least one extra sample to detect state > - * difference on ADC side. > */ > - if (!priv->trig_more_count) { > - int timeout_ms = DIV_ROUND_UP(priv->scan_interval_us, > - USEC_PER_MSEC); > - > - hrtimer_start(&priv->trig_timer, ms_to_ktime(timeout_ms), > - HRTIMER_MODE_REL_SOFT); > - } > - > - enable_irq(priv->spi->irq); > - > - spin_unlock_irqrestore(&priv->trig_lock, flags); > + tim = ns_to_ktime((priv->scan_interval_us - priv->time_per_scan_us) * > + NSEC_PER_USEC); > + hrtimer_start(&priv->trig_timer, tim, HRTIMER_MODE_REL_SOFT); This moves enabling the irq to the first instance of the timer - is that ever too late? > } > > static int tsc2046_adc_set_trigger_state(struct iio_trigger *trig, bool enable) > @@ -493,8 +506,8 @@ static int tsc2046_adc_set_trigger_state(struct iio_trigger *trig, bool enable) > if (enable) { > enable_irq(priv->spi->irq); > } else { > + hrtimer_cancel(&priv->trig_timer); So this will wait for the callback to finish. However, is there a chance of an interrupt just after this but before disable_irq that ends up starting the timer again? > disable_irq(priv->spi->irq); > - hrtimer_try_to_cancel(&priv->trig_timer); > } > > return 0; > @@ -668,10 +681,11 @@ static int tsc2046_adc_probe(struct spi_device *spi) > iio_trigger_set_drvdata(trig, indio_dev); > trig->ops = &tsc2046_adc_trigger_ops; > > - spin_lock_init(&priv->trig_lock); > + spin_lock_init(&priv->state_lock); > + priv->state = TSC2046_STATE_STANDBY; > hrtimer_init(&priv->trig_timer, CLOCK_MONOTONIC, > HRTIMER_MODE_REL_SOFT); > - priv->trig_timer.function = tsc2046_adc_trig_more; > + priv->trig_timer.function = tsc2046_adc_timer; > > ret = devm_iio_trigger_register(dev, trig); > if (ret) {