The pin muxing and clock definitions for the MUSB controller are
not done through the same registers/pin mux options, so this
explicitly configures the registers and pin-mux options for MUSB
on AM3517-EVM
Signed-off-by: Adam Ford
diff --git a/arch/arm/mach-omap2/pdata-quirks.c
b/arch/arm/mach
The glue that connects the AM35xx is not the same as the OMAP3.
With the AM35xx-MUSB now available in device tree, point to that
glue instead of omap3.
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/am3517.dtsi b/arch/arm/boot/dts/am3517.dtsi
index ca294914bbb1..c17cfe6a2132 100644
There are two clocks that fail when attempting to use them. This
patch patches the clock names to match those in hwmods.
Signed-off-by: Adam Ford
diff --git a/drivers/usb/musb/am35x.c b/drivers/usb/musb/am35x.c
index a55db15a8457..56f8e13f4c1b 100644
--- a/drivers/usb/musb/am35x.c
+++ b
With AM35x now supported in device tree and the pdata-quirks
configuring the AM3517 clocks and some of the pin-mux,
this patch enables the MUSB and configures the rest of the pin-
mux options
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/dts/am3517-evm.dts b/arch/arm/boot/dts/am3517
The AM35x glue doesn't yet support device tree, so this patch
adds the basics hooks so it doesn't haven't use pdata-quirks.c
Signed-off-by: Adam Ford
diff --git a/drivers/usb/musb/am35x.c b/drivers/usb/musb/am35x.c
index 660641ab1545..a55db15a8457 100644
--- a/drivers/usb/musb/am35x.c
+++ b
the
register that isn't yet available using device tree to enable
MSUB, then finally modifies the AM3517 and AM3517-EVM to use
the updated AM35x glue to support MUSB.
It currently doesnt' work, but I am looking for ideas on
what I may have missed or done incorrectly.
Adam Ford (5):
usb: musb: am35x
On Thu, Nov 2, 2017 at 2:58 PM, Adam Ford <aford...@gmail.com> wrote:
> On Thu, Nov 2, 2017 at 2:43 PM, Tony Lindgren <t...@atomide.com> wrote:
>> * Bin Liu <b-...@ti.com> [171031 18:35]:
>>> Hi,
>>>
>>> On Tue, Oct 31, 2017 at 12:56:40PM -
On Thu, Nov 2, 2017 at 2:43 PM, Tony Lindgren <t...@atomide.com> wrote:
> * Bin Liu <b-...@ti.com> [171031 18:35]:
>> Hi,
>>
>> On Tue, Oct 31, 2017 at 12:56:40PM -0500, Adam Ford wrote:
>> > We have a situation where occasionally the USB glitches where
We have a situation where occasionally the USB glitches where the D-
glitches low at or near an end of frame (EOF) or end of packet (EOP).
We're using the TWL4030 with MUSB on an OMAP3 processor. We cannot
tell where the glitch is originating.
We're working on resolving this in both hardware
For what it's worth, I tried running the MUSB via the twl4030 on
Linux-Next (I don't remember which snapshot), and it was broken for me
on a DM3730 (OMAP 3630), but Kernel 4.4.2 worked. Are you using
Linux-Next or one of the stable kernels?
I can try again later this week with a newer linux-next
10 matches
Mail list logo
