From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ulrich Hecht <uli+renesas@fpond.eu>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Linux I2C <linux-i2c@vger.kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v3] i2c: sh_mobile: implement atomic transfers
Date: Wed, 23 Sep 2020 16:17:23 +0200 [thread overview]
Message-ID: <CAMuHMdXF7kX0u_awH3w8sCAvAQUN7dzZix6anSrrafwTjpLBUg@mail.gmail.com> (raw)
In-Reply-To: <20200922154943.29574-1-uli+renesas@fpond.eu>
Hi Uli,
On Tue, Sep 22, 2020 at 5:49 PM Ulrich Hecht <uli+renesas@fpond.eu> wrote:
> Implements atomic transfers to fix reboot/shutdown on r8a7790 Lager and
> similar boards.
>
> Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> This is a rebased version of v2 with a minor issue fixed. It does not
> resolve the runtime PM issue that may arise (see "watchdog: da9063: wake up
> parent ahead of reboot", https://patchwork.kernel.org/patch/11749121/ ), but
> in practice it works, and our understanding so far is that this will have to
> be resolved outside this driver and should IMO not block this patch.
See my comment below.
> Changes since v2:
> - rebase
> - make sure time_left is updated
Thanks for the update!
> --- a/drivers/i2c/busses/i2c-sh_mobile.c
> +++ b/drivers/i2c/busses/i2c-sh_mobile.c
> @@ -429,7 +432,8 @@ static irqreturn_t sh_mobile_i2c_isr(int irq, void *dev_id)
>
> if (wakeup) {
> pd->sr |= SW_DONE;
> - wake_up(&pd->wait);
> + if (!pd->atomic_xfer)
> + wake_up(&pd->wait);
> }
>
> /* defeat write posting to avoid spurious WAIT interrupts */
> @@ -581,12 +585,14 @@ static void start_ch(struct sh_mobile_i2c_data *pd, struct i2c_msg *usr_msg,
> pd->pos = -1;
> pd->sr = 0;
>
if (pd->atomic_xfer)
return;
and be done with it?
> - pd->dma_buf = i2c_get_dma_safe_msg_buf(pd->msg, 8);
> - if (pd->dma_buf)
> - sh_mobile_i2c_xfer_dma(pd);
> -
> - /* Enable all interrupts to begin with */
> - iic_wr(pd, ICIC, ICIC_DTEE | ICIC_WAITE | ICIC_ALE | ICIC_TACKE);
> + if (!pd->atomic_xfer) {
> + pd->dma_buf = i2c_get_dma_safe_msg_buf(pd->msg, 8);
> + if (pd->dma_buf)
> + sh_mobile_i2c_xfer_dma(pd);
> + /* Enable all interrupts to begin with */
> + iic_wr(pd, ICIC,
> + ICIC_DTEE | ICIC_WAITE | ICIC_ALE | ICIC_TACKE);
> + }
> }
>
> @@ -696,14 +721,35 @@ static int sh_mobile_i2c_xfer(struct i2c_adapter *adapter,
> return err ?: num;
> }
>
> +static int sh_mobile_i2c_xfer(struct i2c_adapter *adapter,
> + struct i2c_msg *msgs,
> + int num)
> +{
> + struct sh_mobile_i2c_data *pd = i2c_get_adapdata(adapter);
> +
> + pd->atomic_xfer = false;
> + return sh_mobile_xfer(pd, msgs, num);
> +}
> +
> +static int sh_mobile_i2c_xfer_atomic(struct i2c_adapter *adapter,
> + struct i2c_msg *msgs,
> + int num)
> +{
> + struct sh_mobile_i2c_data *pd = i2c_get_adapdata(adapter);
> +
To make sure external conditions are satisfied, and we never deadlock:
if (pd->dev->power.is_suspended)
return -EPERM; /* any other suitable error code? */
Perhaps this can even be done in the i2c core instead?
> + pd->atomic_xfer = true;
> + return sh_mobile_xfer(pd, msgs, num);
> +}
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-09-23 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:49 [PATCH v3] i2c: sh_mobile: implement atomic transfers Ulrich Hecht
2020-09-22 16:29 ` Wolfram Sang
2020-09-23 14:17 ` Geert Uytterhoeven [this message]
2020-09-23 16:06 ` Wolfram Sang
2020-09-23 19:05 ` Geert Uytterhoeven
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=CAMuHMdXF7kX0u_awH3w8sCAvAQUN7dzZix6anSrrafwTjpLBUg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=uli+renesas@fpond.eu \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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).