Re: [PATCH 1/5] mmc: sdhci-pxav3: fix optional clock name

2015-10-16 Thread Sebastian Hesselbarth
On 16.10.2015 13:40, Jisheng Zhang wrote: On Thu, 15 Oct 2015 23:41:22 +0200 Sebastian Hesselbarth wrote: On 12.10.2015 07:46, Jisheng Zhang wrote: Commit 8afdc9cca27f ("mmc: sdhci-pxav3: Get optional core clock") adds additional optional clock support, but the clock names isn't correct. The

Re: [PATCH 1/5] mmc: sdhci-pxav3: fix optional clock name

2015-10-16 Thread Jisheng Zhang
Dear Sebastian, On Thu, 15 Oct 2015 23:41:22 +0200 Sebastian Hesselbarth wrote: > On 12.10.2015 07:46, Jisheng Zhang wrote: > > Commit 8afdc9cca27f ("mmc: sdhci-pxav3: Get optional core clock") adds > > additional optional clock support, but the clock names isn't correct. > > The current "io" c

Re: [PATCH 1/5] mmc: sdhci-pxav3: fix optional clock name

2015-10-15 Thread Sebastian Hesselbarth
On 12.10.2015 07:46, Jisheng Zhang wrote: Commit 8afdc9cca27f ("mmc: sdhci-pxav3: Get optional core clock") adds additional optional clock support, but the clock names isn't correct. The current "io" clock is really the PXAv3 SDHCI IP's "core" clock which is manadatory. The current "core" clock

[PATCH 1/5] mmc: sdhci-pxav3: fix optional clock name

2015-10-11 Thread Jisheng Zhang
Commit 8afdc9cca27f ("mmc: sdhci-pxav3: Get optional core clock") adds additional optional clock support, but the clock names isn't correct. The current "io" clock is really the PXAv3 SDHCI IP's "core" clock which is manadatory. The current "core" clock is really the IP's "axi" clock which is opti