Re: [PATCH 30/41] usb: musb: ux500: Don't supply a con_id whenrequesting the clock
From: Linus Walleij
Date: Fri Sep 20 2013 - 16:41:24 EST
On Wed, Sep 18, 2013 at 2:14 PM, Lee Jones <lee.jones@xxxxxxxxxx> wrote:
> If we supply a con_id then the clock framework will search for that name
> in MUSB's Device Tree node for the 'clock-names' property. If it's absent
> the clock request will fail. However, if we don't supply the con_id then
> clk_get() will call into clk_sys() which will use the device name to
> search for the appropriate clock, which is much more natural than forcing
> 'usb'.
>
> Cc: Felipe Balbi <balbi@xxxxxx>
> Signed-off-by: Lee Jones <lee.jones@xxxxxxxxxx>
Looks fine to me, Felipe can we have your ACK on this so I can take
this with the rest of the clock stuff through ARM SoC?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/