From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>, Samuel Holland <samuel@sholland.org>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v3 3/3] bus: sunxi-rsb: Clear interrupt status before each transfer
Date: Tue, 15 Nov 2022 22:38:29 +0100 [thread overview]
Message-ID: <1910101.PYKUYFuaPT@jernej-laptop> (raw)
In-Reply-To: <735349b0-6738-8ace-a7d3-aafae2a62501@sholland.org>
Dne torek, 15. november 2022 ob 07:08:12 CET je Samuel Holland napisal(a):
> On 11/14/22 15:00, Jernej Škrabec wrote:
> > Hi Samuel,
> >
> > Dne ponedeljek, 14. november 2022 ob 02:57:49 CET je Samuel Holland
> >
> > napisal(a):
> >> Currently, the driver clears the interrupt status bits after anything
> >> could have set them. However, this requires duplicating the same logic
> >> in several places.
> >>
> >> Instead of clearing the status flags in the interrupt handler, disable
> >> all further interrupts by clearing the RSB_CTRL_GLOBAL_INT_ENB bit.
> >
> > where is this bit cleared?
>
> It is cleared by any write to RSB_CTRL that does not include it. I noted
> it below with the "disable interrupts" comments.
Right.
>
> >> Then we can delay the status register write until the start of the next
> >> transfer, so it only has to be done in one place.
> >>
> >> Signed-off-by: Samuel Holland <samuel@sholland.org>
> >> ---
> >>
> >> Changes in v3:
> >> - Add a patch refactoring how the status bits are cleared
> >>
> >> drivers/bus/sunxi-rsb.c | 20 +++++---------------
> >> 1 file changed, 5 insertions(+), 15 deletions(-)
> >>
> >> diff --git a/drivers/bus/sunxi-rsb.c b/drivers/bus/sunxi-rsb.c
> >> index 3aa91aed3bf7..cb622e60897b 100644
> >> --- a/drivers/bus/sunxi-rsb.c
> >> +++ b/drivers/bus/sunxi-rsb.c
> >> @@ -279,6 +279,7 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb *rsb)
> >>
> >> int_mask = RSB_INTS_LOAD_BSY | RSB_INTS_TRANS_ERR |
> >> RSB_INTS_TRANS_OVER;
> >> writel(int_mask, rsb->regs + RSB_INTE);
> >>
> >> + writel(int_mask, rsb->regs + RSB_INTS);
> >
> > Wouldn't be better to clear status before enabling interrupts? Unless
> > global interrupt flag is cleared beforehand, but I don't see that
> > anywhere.
> Indeed the intention was that the global interrupt flag is cleared
> beforehand, and only enabled on the next line below. However, I realize
> I missed disabling it for the new atomic case.
>
> I'm not so sure anymore that this patch is an improvement. What do you
> think? I can send a v4 with a fix, or I am fine with skipping this
> patch. I would at least like the other two to be merged for -fixes.
Sure, first two patches will go in regardless. I'm not convinced of value of
this patch either. I guess we can skip it.
Best regards,
Jernej
>
> Regards,
> Samuel
>
> >> writel(RSB_CTRL_START_TRANS | RSB_CTRL_GLOBAL_INT_ENB,
> >>
> >> rsb->regs + RSB_CTRL);
> >>
> >> @@ -286,7 +287,6 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb *rsb)
> >>
> >> timeout = readl_poll_timeout_atomic(rsb->regs +
RSB_INTS,
> >>
> >>
status, (status & int_mask),
> >> 10,
100000);
> >>
> >> - writel(status, rsb->regs + RSB_INTS);
> >>
> >> } else {
> >>
> >> timeout = !wait_for_completion_io_timeout(&rsb-
> >>
> >> complete,
> >>
> >>
msecs_to_jiffies(100));
> >>
> >> @@ -296,12 +296,9 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb
> >> *rsb)
> >>
> >> if (timeout) {
> >>
> >> dev_dbg(rsb->dev, "RSB timeout\n");
> >>
> >> - /* abort the transfer */
> >> + /* abort the transfer and disable interrupts */
> >>
> >> writel(RSB_CTRL_ABORT_TRANS, rsb->regs + RSB_CTRL);
> >>
> >> - /* clear any interrupt flags */
> >> - writel(readl(rsb->regs + RSB_INTS), rsb->regs +
RSB_INTS);
> >> -
> >>
> >> return -ETIMEDOUT;
> >>
> >> }
> >>
> >> @@ -503,15 +500,11 @@ EXPORT_SYMBOL_GPL(__devm_regmap_init_sunxi_rsb);
> >>
> >> static irqreturn_t sunxi_rsb_irq(int irq, void *dev_id)
> >> {
> >>
> >> struct sunxi_rsb *rsb = dev_id;
> >>
> >> - u32 status;
> >>
> >> - status = readl(rsb->regs + RSB_INTS);
> >> - rsb->status = status;
> >> + /* disable interrupts */
> >> + writel(0, rsb->regs + RSB_CTRL);
> >>
> >> - /* Clear interrupts */
> >> - status &= (RSB_INTS_LOAD_BSY | RSB_INTS_TRANS_ERR |
> >> - RSB_INTS_TRANS_OVER);
> >> - writel(status, rsb->regs + RSB_INTS);
> >> + rsb->status = readl(rsb->regs + RSB_INTS);
> >>
> >> complete(&rsb->complete);
> >>
> >> @@ -532,9 +525,6 @@ static int sunxi_rsb_init_device_mode(struct
> >> sunxi_rsb
> >> *rsb) if (reg & RSB_DMCR_DEVICE_START)
> >>
> >> ret = -ETIMEDOUT;
> >>
> >> - /* clear interrupt status bits */
> >> - writel(readl(rsb->regs + RSB_INTS), rsb->regs + RSB_INTS);
> >> -
> >>
> >> return ret;
> >>
> >> }
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>, Samuel Holland <samuel@sholland.org>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v3 3/3] bus: sunxi-rsb: Clear interrupt status before each transfer
Date: Tue, 15 Nov 2022 22:38:29 +0100 [thread overview]
Message-ID: <1910101.PYKUYFuaPT@jernej-laptop> (raw)
In-Reply-To: <735349b0-6738-8ace-a7d3-aafae2a62501@sholland.org>
Dne torek, 15. november 2022 ob 07:08:12 CET je Samuel Holland napisal(a):
> On 11/14/22 15:00, Jernej Škrabec wrote:
> > Hi Samuel,
> >
> > Dne ponedeljek, 14. november 2022 ob 02:57:49 CET je Samuel Holland
> >
> > napisal(a):
> >> Currently, the driver clears the interrupt status bits after anything
> >> could have set them. However, this requires duplicating the same logic
> >> in several places.
> >>
> >> Instead of clearing the status flags in the interrupt handler, disable
> >> all further interrupts by clearing the RSB_CTRL_GLOBAL_INT_ENB bit.
> >
> > where is this bit cleared?
>
> It is cleared by any write to RSB_CTRL that does not include it. I noted
> it below with the "disable interrupts" comments.
Right.
>
> >> Then we can delay the status register write until the start of the next
> >> transfer, so it only has to be done in one place.
> >>
> >> Signed-off-by: Samuel Holland <samuel@sholland.org>
> >> ---
> >>
> >> Changes in v3:
> >> - Add a patch refactoring how the status bits are cleared
> >>
> >> drivers/bus/sunxi-rsb.c | 20 +++++---------------
> >> 1 file changed, 5 insertions(+), 15 deletions(-)
> >>
> >> diff --git a/drivers/bus/sunxi-rsb.c b/drivers/bus/sunxi-rsb.c
> >> index 3aa91aed3bf7..cb622e60897b 100644
> >> --- a/drivers/bus/sunxi-rsb.c
> >> +++ b/drivers/bus/sunxi-rsb.c
> >> @@ -279,6 +279,7 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb *rsb)
> >>
> >> int_mask = RSB_INTS_LOAD_BSY | RSB_INTS_TRANS_ERR |
> >> RSB_INTS_TRANS_OVER;
> >> writel(int_mask, rsb->regs + RSB_INTE);
> >>
> >> + writel(int_mask, rsb->regs + RSB_INTS);
> >
> > Wouldn't be better to clear status before enabling interrupts? Unless
> > global interrupt flag is cleared beforehand, but I don't see that
> > anywhere.
> Indeed the intention was that the global interrupt flag is cleared
> beforehand, and only enabled on the next line below. However, I realize
> I missed disabling it for the new atomic case.
>
> I'm not so sure anymore that this patch is an improvement. What do you
> think? I can send a v4 with a fix, or I am fine with skipping this
> patch. I would at least like the other two to be merged for -fixes.
Sure, first two patches will go in regardless. I'm not convinced of value of
this patch either. I guess we can skip it.
Best regards,
Jernej
>
> Regards,
> Samuel
>
> >> writel(RSB_CTRL_START_TRANS | RSB_CTRL_GLOBAL_INT_ENB,
> >>
> >> rsb->regs + RSB_CTRL);
> >>
> >> @@ -286,7 +287,6 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb *rsb)
> >>
> >> timeout = readl_poll_timeout_atomic(rsb->regs +
RSB_INTS,
> >>
> >>
status, (status & int_mask),
> >> 10,
100000);
> >>
> >> - writel(status, rsb->regs + RSB_INTS);
> >>
> >> } else {
> >>
> >> timeout = !wait_for_completion_io_timeout(&rsb-
> >>
> >> complete,
> >>
> >>
msecs_to_jiffies(100));
> >>
> >> @@ -296,12 +296,9 @@ static int _sunxi_rsb_run_xfer(struct sunxi_rsb
> >> *rsb)
> >>
> >> if (timeout) {
> >>
> >> dev_dbg(rsb->dev, "RSB timeout\n");
> >>
> >> - /* abort the transfer */
> >> + /* abort the transfer and disable interrupts */
> >>
> >> writel(RSB_CTRL_ABORT_TRANS, rsb->regs + RSB_CTRL);
> >>
> >> - /* clear any interrupt flags */
> >> - writel(readl(rsb->regs + RSB_INTS), rsb->regs +
RSB_INTS);
> >> -
> >>
> >> return -ETIMEDOUT;
> >>
> >> }
> >>
> >> @@ -503,15 +500,11 @@ EXPORT_SYMBOL_GPL(__devm_regmap_init_sunxi_rsb);
> >>
> >> static irqreturn_t sunxi_rsb_irq(int irq, void *dev_id)
> >> {
> >>
> >> struct sunxi_rsb *rsb = dev_id;
> >>
> >> - u32 status;
> >>
> >> - status = readl(rsb->regs + RSB_INTS);
> >> - rsb->status = status;
> >> + /* disable interrupts */
> >> + writel(0, rsb->regs + RSB_CTRL);
> >>
> >> - /* Clear interrupts */
> >> - status &= (RSB_INTS_LOAD_BSY | RSB_INTS_TRANS_ERR |
> >> - RSB_INTS_TRANS_OVER);
> >> - writel(status, rsb->regs + RSB_INTS);
> >> + rsb->status = readl(rsb->regs + RSB_INTS);
> >>
> >> complete(&rsb->complete);
> >>
> >> @@ -532,9 +525,6 @@ static int sunxi_rsb_init_device_mode(struct
> >> sunxi_rsb
> >> *rsb) if (reg & RSB_DMCR_DEVICE_START)
> >>
> >> ret = -ETIMEDOUT;
> >>
> >> - /* clear interrupt status bits */
> >> - writel(readl(rsb->regs + RSB_INTS), rsb->regs + RSB_INTS);
> >> -
> >>
> >> return ret;
> >>
> >> }
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-15 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 1:57 [PATCH v3 0/3] bus: sunxi-rsb: Fix poweroff issues Samuel Holland
2022-11-14 1:57 ` Samuel Holland
2022-11-14 1:57 ` [PATCH v3 1/3] bus: sunxi-rsb: Remove the shutdown callback Samuel Holland
2022-11-14 1:57 ` Samuel Holland
2022-11-14 1:57 ` [PATCH v3 2/3] bus: sunxi-rsb: Support atomic transfers Samuel Holland
2022-11-14 1:57 ` Samuel Holland
2022-11-14 20:49 ` Jernej Škrabec
2022-11-14 20:49 ` Jernej Škrabec
2022-11-14 1:57 ` [PATCH v3 3/3] bus: sunxi-rsb: Clear interrupt status before each transfer Samuel Holland
2022-11-14 1:57 ` Samuel Holland
2022-11-14 21:00 ` Jernej Škrabec
2022-11-14 21:00 ` Jernej Škrabec
2022-11-15 6:08 ` Samuel Holland
2022-11-15 6:08 ` Samuel Holland
2022-11-15 21:38 ` Jernej Škrabec [this message]
2022-11-15 21:38 ` Jernej Škrabec
2022-11-16 18:29 ` [PATCH v3 0/3] bus: sunxi-rsb: Fix poweroff issues Jernej Škrabec
2022-11-16 18:29 ` Jernej Škrabec
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=1910101.PYKUYFuaPT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.