RE: [PATCH v2 2/3] mmc: sh_mobile_sdhi: explain clock bindings

2017-01-18 Thread Chris Brandt
Hi Geert, On Wednesday, January 18, 2017, Geert Uytterhoeven wrote: > > +- clocks: Most controllers only have 1 clock source per cahnnel. > However, some > > + have 2. If 2 clocks are specified, you must name them as > "core" and > > + "carddetect". If the controller only has 1

RE: [PATCH v2 2/3] mmc: sh_mobile_sdhi: explain clock bindings

2017-01-18 Thread Chris Brandt
Hi Wolfram, On Tuesday, January 17, 2017, Wolfram Sang wrote: > > +- clocks: Most controllers only have 1 clock source per cahnnel. > > +However, some > > channel. > > > + have 2. If 2 clocks are specified, you must name them as "core" > > +and > > Maybe "However, some have a second clock

Re: [PATCH v2 2/3] mmc: sh_mobile_sdhi: explain clock bindings

2017-01-17 Thread Wolfram Sang
On Tue, Jan 17, 2017 at 02:59:39PM -0500, Chris Brandt wrote: > In the case of a single clock source, you don't need names. However, > if the controller has 2 clock sources, you need to name them correctly > so the driver can find the 2nd one. > > Signed-off-by: Chris Brandt

[PATCH v2 2/3] mmc: sh_mobile_sdhi: explain clock bindings

2017-01-17 Thread Chris Brandt
In the case of a single clock source, you don't need names. However, if the controller has 2 clock sources, you need to name them correctly so the driver can find the 2nd one. Signed-off-by: Chris Brandt --- Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 21