From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Hecht <uli+renesas@fpond.eu>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: sh_mobile: implement atomic transfers
Date: Tue, 30 Jun 2020 21:45:28 +0200 [thread overview]
Message-ID: <20200630194528.GB999@ninjato> (raw)
In-Reply-To: <20200625151658.GB1041@ninjato>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Thu, Jun 25, 2020 at 05:16:58PM +0200, Wolfram Sang wrote:
> Hi Geert,
>
> I spend some more thoughts on this.
>
> > > > In general, pm_runtime_get_sync() is not safe to call from atomic
> > > > context.
> > > > For Renesas SoCs, I think both the power and clock domains are safe, as
> > > > the respective drivers don't sleep. The PM core might, though.
> > >
> > > Still, that sounds to me like we should protect these calls as in V1?
>
> I still think we should guard these calls just because it is not safe to
> call them from atomic contexts.
>
> > And talk to the i2c controller while it is disabled?
>
> Is there maybe some "always-on" property which we could add to the
> respective IIC clock?
Ping to this question...
>
> > That does seem to work on R-Car Gen2 (similar to SMP bringup accessing
> > registers of a disabled WDT?), though.
>
> Yes. Uli's patch will not cause a regression because we are already
> calling i2c_transfer very late. And we do call the runtime_pm functions
> currently. So, it will improve the situation there.
>
> > Needs testing on R-Mobile A1....
>
> That's armadillo, right? I don't have that, sadly.
>
> Thanks,
>
> Wolfram
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-30 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 15:05 [PATCH v2] i2c: sh_mobile: implement atomic transfers Ulrich Hecht
2020-06-18 16:39 ` Geert Uytterhoeven
2020-06-21 11:39 ` Geert Uytterhoeven
2020-06-25 6:59 ` Wolfram Sang
2020-06-25 7:06 ` Wolfram Sang
2020-06-25 8:18 ` Geert Uytterhoeven
2020-06-25 8:33 ` Wolfram Sang
2020-06-25 15:16 ` Wolfram Sang
2020-06-30 19:45 ` Wolfram Sang [this message]
2020-06-30 19:58 ` 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=20200630194528.GB999@ninjato \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=uli+renesas@fpond.eu \
/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