From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] spi: s3c64xx: modified error interrupt handling and init
Date: Thu, 07 Feb 2013 12:09:11 +0100 [thread overview]
Message-ID: <1585017.derjdP1mHL@amdc1227> (raw)
In-Reply-To: <CAKrE-KdX+Nxk0X4xdz6Dx3WVtOpV+ms+gPB-Dq-MwZwetyZ5Nw@mail.gmail.com>
Hi Girish,
On Wednesday 06 of February 2013 12:12:29 Girish KS wrote:
> On Wed, Feb 6, 2013 at 2:26 AM, Grant Likely <grant.likely@secretlab.ca>
wrote:
> > On Tue, 5 Feb 2013 15:09:41 -0800, Girish K S
<girishks2000@gmail.com> 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@samsung.com>
> >> ---
> >>
> >> 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?
> The user manual says, wirting 1 to the pending clear register clears
> the interrupt (its not auto clear to 0). so i need to explicitly reset
> those bits thats what the 2nd write does
I have looked through user's manuals of different Samsung SoCs. All of
them said that writing 1 to a bit clears the corresponding interrupt, but
none of them contain any note that it must be manually cleared to 0.
In addition the expression
clr & ~clr
makes no sense, because it is equal to 0.
If you really need to clear those bits manually (and I don't think so),
you should replace this expression with 0.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform
next prev parent reply other threads:[~2013-02-07 11:09 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 1/4] spi: s3c64xx: modified error interrupt handling and init Girish K S
2013-02-06 10:26 ` Grant Likely
2013-02-06 20:12 ` Girish KS
2013-02-06 23:48 ` Grant Likely
2013-02-07 0:33 ` Girish KS
2013-02-08 1:04 ` Girish KS
2013-02-08 8:16 ` Girish KS
2013-02-07 11:09 ` Tomasz Figa [this message]
2013-02-07 17:46 ` Girish KS
2013-02-08 8:33 ` Tomasz Figa
2013-02-08 8:58 ` Girish KS
2013-02-08 9:26 ` Girish KS
2013-02-05 23:09 ` [PATCH 2/4] spi: s3c64xx: added support for polling mode Girish K S
2013-02-06 10:35 ` Grant Likely
2013-02-06 22:04 ` Girish KS
2013-02-05 23:09 ` [PATCH 3/4] spi: s3c64xx: add gpio quirk for controller Girish K S
2013-02-06 10:40 ` Grant Likely
2013-02-06 22:38 ` Girish KS
2013-02-07 11:55 ` Mark Brown
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=1585017.derjdP1mHL@amdc1227 \
--to=t.figa@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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