[...]
>> Ahh, I see.
>>
>> It seems like a reasonable assumption that the controller can't cope
>> with a higher clock rate than 100 MHz as "input" clock. That would
>> then mean that there are different versions of the controller, as it
>> seems like for some version it's fine with 200MHz and
On Fri, Nov 13, 2015 at 4:31 AM, Ulf Hansson wrote:
> On 12 November 2015 at 20:44, Alan Cooper wrote:
>> On Thu, Nov 12, 2015 at 4:35 AM, Ulf Hansson wrote:
>>> On 6 November 2015 at 19:56, Al Cooper
From: Thierry Reding
The data in the SoC description structures is static and can therefore
reside in read-only memory.
Signed-off-by: Thierry Reding
---
drivers/mmc/host/sdhci-tegra.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff
From: Thierry Reding
Signed-off-by: Thierry Reding
---
drivers/mmc/host/sdhci-tegra.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c
index 8d49d9af6f54..368f1b74a525
On 15 November 2015 at 14:53, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate kernel thread. PM core ensures
> all