From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Ulrich Hecht <uli+renesas@fpond.eu>,
Simon Horman <horms+renesas@verge.net.au>,
Niklas Soderlund <niklas.soderlund@ragnatech.se>
Subject: Re: [PATCH 2/2] mmc: tmio: Make sure the PM domain is 'started' while probing
Date: Mon, 25 May 2020 12:04:08 +0200 [thread overview]
Message-ID: <20200525100408.GA1149@ninjato> (raw)
In-Reply-To: <CAPDyKFrzY67it3UbDDTCe-z95_sKO5EQaiGm=6NbmPDJ8fFqcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
> > Note that this does mean that all PM domain providers that do not rely
> > on pm_clk, but have their own start/stop methods, need to be aware of
> > this quirk, and should take care of reference counting themselves.
> > Fortunately there seems to be only one:
> > drivers/soc/ti/ti_sci_pm_domains.c.
> > Unfortunately it doesn't do reference counting, so if that PM domain
> > driver is ever used with a driver that calls dev_pm_domain_start(),
> > mysterious things may happen...
>
> Good point. Perhaps we should document this somewhere.
I haven't understood all of the details, but Geert's description sounds
like we definately should document this. Anyone up for it? Otherwise
I'll dig more into it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-25 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 15:24 [PATCH 2/2] mmc: tmio: Make sure the PM domain is 'started' while probing Ulf Hansson
2020-05-19 16:38 ` Wolfram Sang
2020-05-20 11:35 ` Ulf Hansson
2020-05-20 15:57 ` Geert Uytterhoeven
2020-05-20 16:11 ` Ulf Hansson
2020-05-20 17:42 ` Geert Uytterhoeven
2020-05-25 8:47 ` Ulf Hansson
2020-05-25 10:04 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-15 14:04 Ulf Hansson
2020-05-18 20:22 ` Wolfram Sang
2020-05-19 7:50 ` Ulf Hansson
2020-05-19 8:46 ` Wolfram Sang
2020-05-19 8:53 ` Geert Uytterhoeven
2020-05-19 9:09 ` Wolfram Sang
2020-05-19 9:15 ` Ulf Hansson
2020-05-19 9:21 ` Ulf Hansson
2020-05-19 11:32 ` Wolfram Sang
2020-05-19 11:35 ` Wolfram Sang
2020-05-19 13:54 ` Ulf Hansson
2020-05-18 21:07 ` Geert Uytterhoeven
2020-05-19 8:18 ` Ulf Hansson
2020-05-19 8:29 ` 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=20200525100408.GA1149@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulf.hansson@linaro.org \
--cc=uli+renesas@fpond.eu \
--cc=yamada.masahiro@socionext.com \
/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.