[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 10 Oct 2015 15:05:35 +0800
From: Jisheng Zhang <jszhang@...vell.com>
To: Marcin Wojtas <mw@...ihalf.com>
CC: <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Andrew Lunn <andrew@...n.ch>,
"Ulf Hansson" <ulf.hansson@...aro.org>,
Jason Cooper <jason@...edaemon.net>,
Tawfik Bayouk <tawfik@...vell.com>,
Grzegorz Jaszczyk <jaz@...ihalf.com>, <nadavh@...vell.com>,
Lior Amsalem <alior@...vell.com>,
Gregory Clément
<gregory.clement@...e-electrons.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH v2 2/5] mmc: sdhci-pxav3: enable usage of DAT3 pin as HW
card detect
Hi Marcin,
On Fri, 9 Oct 2015 16:45:25 +0200
Marcin Wojtas <mw@...ihalf.com> wrote:
> Jisheng,
>
>
> >>
> >> When using DAT3-based detection Armada 38x SDIO IP expects its internal
> >> clock to be always on, which had to be ensured twofold:
> >
> > What happen if runtime suspend disables its core clk and axi clk? I guess
> > dat3-based detection isn't compatible with runtime pm. If so, do we also
> > need to disable runtime pm in probe function?
>
> Is runtime resume supposed to be triggered by card detection? Is there
I think so. Take marvell berlin for example, card insert => gpio interrupt
or => sdhci runtime resume.
> a way to manually trigger runtime suspend and resume of sdhci? Anyway
If runtime-pm is builtin and the host driver supports runtime-pm (sdhci-pxav3
supports runtime-pm well), when there's no sdhc transactions, runtime suspend
will be triggered automatically after some time (50ms?)
> coreclk is not a problem, as it's not used by A38x.
I checked A38x dts files, it's <&gateclk 17>. So the question is: what will
happen if <&gateclk 17> is disabled in runtime suspend? Is the dat3-based
CD still works? In theory, it should not work any more.
>
> >
> >> - Each time controller is reset by updating appropriate registers. On the
> >> occasion of adding new register @0x104, register @0x100 name is modified
> >> in order to the be aligned with Armada 38x documentation.
> >> - Leaving the clock enabled despite power-down. For this purpose a new
> >> quirk had to be added to SDHCI subsystem - SDHCI_QUIRK2_KEEP_INT_CLK_ON.
> >
> > As seen from other mails, Ulf calls for no more quirks...
> >
>
> Ok, I'll try to find another solution.
>
> Best regards,
> Marcin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists