On Wed, 2017-01-25 at 00:23 +0100, Matthias Brugger wrote:
>
> On 01/20/2017 03:20 AM, Chunfeng Yun wrote:
> > On Thu, 2017-01-19 at 13:22 +0100, Matthias Brugger wrote:
> >>
> >> On 18/01/17 07:08, Chunfeng Yun wrote:
> >>> usually, the reference clock comes from 26M oscillator directly,
> >>> bu
On 01/20/2017 03:20 AM, Chunfeng Yun wrote:
On Thu, 2017-01-19 at 13:22 +0100, Matthias Brugger wrote:
On 18/01/17 07:08, Chunfeng Yun wrote:
usually, the reference clock comes from 26M oscillator directly,
but some SoCs are not, add it for compatibility.
Signed-off-by: Chunfeng Yun
---
d
On Thu, 2017-01-19 at 13:22 +0100, Matthias Brugger wrote:
>
> On 18/01/17 07:08, Chunfeng Yun wrote:
> > usually, the reference clock comes from 26M oscillator directly,
> > but some SoCs are not, add it for compatibility.
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > drivers/usb/mtu3/mtu3.h
On 18/01/17 07:08, Chunfeng Yun wrote:
usually, the reference clock comes from 26M oscillator directly,
but some SoCs are not, add it for compatibility.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h |1 +
drivers/usb/mtu3/mtu3_plat.c | 21 +++--
2 files c
usually, the reference clock comes from 26M oscillator directly,
but some SoCs are not, add it for compatibility.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h |1 +
drivers/usb/mtu3/mtu3_plat.c | 21 +++--
2 files changed, 20 insertions(+), 2 deletions(-)
d