From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Girish K S <girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/4] spi: s3c64xx: modified error interrupt handling and init
Date: Wed, 06 Feb 2013 10:26:28 +0000 [thread overview]
Message-ID: <20130206102628.5E7413E1510@localhost> (raw)
In-Reply-To: <1360105784-12282-2-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
On Tue, 5 Feb 2013 15:09:41 -0800, Girish K S <girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> The status of the interrupt is available in the status register,
> so reading the clear pending register and writing back the same
> value will not actually clear the pending interrupts. This patch
> modifies the interrupt handler to read the status register and
> clear the corresponding pending bit in the clear pending register.
>
> Modified the hwInit function to clear all the pending interrupts.
>
> Signed-off-by: Girish K S <ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> ---
> drivers/spi/spi-s3c64xx.c | 41 +++++++++++++++++++++++++----------------
> 1 file changed, 25 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index ad93231..b770f88 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -997,25 +997,30 @@ static irqreturn_t s3c64xx_spi_irq(int irq, void *data)
> {
> struct s3c64xx_spi_driver_data *sdd = data;
> struct spi_master *spi = sdd->master;
> - unsigned int val;
> + unsigned int val, clr = 0;
>
> - val = readl(sdd->regs + S3C64XX_SPI_PENDING_CLR);
> + val = readl(sdd->regs + S3C64XX_SPI_STATUS);
>
> - val &= S3C64XX_SPI_PND_RX_OVERRUN_CLR |
> - S3C64XX_SPI_PND_RX_UNDERRUN_CLR |
> - S3C64XX_SPI_PND_TX_OVERRUN_CLR |
> - S3C64XX_SPI_PND_TX_UNDERRUN_CLR;
> -
> - writel(val, sdd->regs + S3C64XX_SPI_PENDING_CLR);
> -
> - if (val & S3C64XX_SPI_PND_RX_OVERRUN_CLR)
> + if (val & S3C64XX_SPI_ST_RX_OVERRUN_ERR) {
> + clr = S3C64XX_SPI_PND_RX_OVERRUN_CLR;
> dev_err(&spi->dev, "RX overrun\n");
> - if (val & S3C64XX_SPI_PND_RX_UNDERRUN_CLR)
> + }
> + if (val & S3C64XX_SPI_ST_RX_UNDERRUN_ERR) {
> + clr |= S3C64XX_SPI_PND_RX_UNDERRUN_CLR;
> dev_err(&spi->dev, "RX underrun\n");
> - if (val & S3C64XX_SPI_PND_TX_OVERRUN_CLR)
> + }
> + if (val & S3C64XX_SPI_ST_TX_OVERRUN_ERR) {
> + clr |= S3C64XX_SPI_PND_TX_OVERRUN_CLR;
> dev_err(&spi->dev, "TX overrun\n");
> - if (val & S3C64XX_SPI_PND_TX_UNDERRUN_CLR)
> + }
> + if (val & S3C64XX_SPI_ST_TX_UNDERRUN_ERR) {
> + clr |= S3C64XX_SPI_PND_TX_UNDERRUN_CLR;
> dev_err(&spi->dev, "TX underrun\n");
> + }
> +
> + /* Clear the pending irq by setting and then clearing it */
> + writel(clr, sdd->regs + S3C64XX_SPI_PENDING_CLR);
> + writel(clr & ~clr, sdd->regs + S3C64XX_SPI_PENDING_CLR);
Wait, what? clr & ~clr == 0 Always. What are you actually trying to do here?
>
> return IRQ_HANDLED;
> }
> @@ -1039,9 +1044,13 @@ static void s3c64xx_spi_hwinit(struct s3c64xx_spi_driver_data *sdd, int channel)
> writel(0, regs + S3C64XX_SPI_MODE_CFG);
> writel(0, regs + S3C64XX_SPI_PACKET_CNT);
>
> - /* Clear any irq pending bits */
> - writel(readl(regs + S3C64XX_SPI_PENDING_CLR),
> - regs + S3C64XX_SPI_PENDING_CLR);
> + /* Clear any irq pending bits, should set and clear the bits */
> + val = S3C64XX_SPI_PND_RX_OVERRUN_CLR |
> + S3C64XX_SPI_PND_RX_UNDERRUN_CLR |
> + S3C64XX_SPI_PND_TX_OVERRUN_CLR |
> + S3C64XX_SPI_PND_TX_UNDERRUN_CLR;
> + writel(val, regs + S3C64XX_SPI_PENDING_CLR);
> + writel(val & ~val, regs + S3C64XX_SPI_PENDING_CLR);
Ditto.
g.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
next prev parent reply other threads:[~2013-02-06 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 23:09 [PATCH 0/4] Add polling support for 64xx spi controller Girish K S
2013-02-05 23:09 ` [PATCH 2/4] spi: s3c64xx: added support for polling mode Girish K S
[not found] ` <1360105784-12282-3-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:35 ` Grant Likely
2013-02-06 22:04 ` Girish KS
[not found] ` <1360105784-12282-1-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-05 23:09 ` [PATCH 1/4] spi: s3c64xx: modified error interrupt handling and init Girish K S
[not found] ` <1360105784-12282-2-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:26 ` Grant Likely [this message]
2013-02-06 20:12 ` Girish KS
[not found] ` <CAKrE-KdX+Nxk0X4xdz6Dx3WVtOpV+ms+gPB-Dq-MwZwetyZ5Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-06 23:48 ` Grant Likely
[not found] ` <CACxGe6uOaoRbtuovEsA87d-MtCbGNd3KZCeHXbBQaEpp6NZ7fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-07 0:33 ` Girish KS
2013-02-08 1:04 ` Girish KS
[not found] ` <CAKrE-KfvywLa4xTwCGzan9OfevzBdY8Z2EO2Mc2VaFm5y0XEzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 8:16 ` Girish KS
2013-02-07 11:09 ` Tomasz Figa
2013-02-07 17:46 ` Girish KS
[not found] ` <CAKrE-KfyGCi_+FozSpGTy0A0VJP=Jq-1SHmvKJU02iJKWHcvLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 8:33 ` Tomasz Figa
2013-02-08 8:58 ` Girish KS
[not found] ` <CAKrE-Kd-mNv=_YkM7GjicgDx=0hqbp5B6qwEvcRzhuSibRNaZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 9:26 ` Girish KS
2013-02-05 23:09 ` [PATCH 3/4] spi: s3c64xx: add gpio quirk for controller Girish K S
[not found] ` <1360105784-12282-4-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:40 ` Grant Likely
2013-02-06 22:38 ` Girish KS
2013-02-07 11:55 ` Mark Brown
[not found] ` <20130207115546.GA3801-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-02-07 18:54 ` Girish KS
2013-02-08 13:17 ` Mark Brown
2013-02-05 23:09 ` [PATCH 4/4] spi: s3c64xx: add support for exynos5440 spi Girish K S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130206102628.5E7413E1510@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).