[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200819125301.GI18122@kozik-lap>
Date: Wed, 19 Aug 2020 14:53:01 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Łukasz Stelmach <l.stelmach@...sung.com>
Cc: Kukjin Kim <kgene@...nel.org>, Andi Shyti <andi@...zian.org>,
Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
m.szyprowski@...sung.com, b.zolnierkie@...sung.com
Subject: Re: [PATCH 8/8] spi: spi-s3c64xx: Turn on interrupts upon resume
On Wed, Aug 19, 2020 at 02:32:08PM +0200, Łukasz Stelmach wrote:
> Signed-off-by: Łukasz Stelmach <l.stelmach@...sung.com>
> ---
> drivers/spi/spi-s3c64xx.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index 27db1e0f6f32..5dcad43fb847 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -1356,6 +1356,10 @@ static int s3c64xx_spi_runtime_resume(struct device *dev)
>
> s3c64xx_spi_hwinit(sdd);
>
> + writel(S3C64XX_SPI_INT_RX_OVERRUN_EN | S3C64XX_SPI_INT_RX_UNDERRUN_EN |
> + S3C64XX_SPI_INT_TX_OVERRUN_EN | S3C64XX_SPI_INT_TX_UNDERRUN_EN,
> + sdd->regs + S3C64XX_SPI_INT_EN);
> +
Makes sense but you should explain in the commit msg what happens
without this (or why they are not enabled).
Best regards,
Krzysztof
Powered by blists - more mailing lists