To be able to call these four helper functions from the M-USB AM35xx
glue code, their declarations need to be moved to a header file in the
kernels include hierarchy.
Signed-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
arch/arm/mach-omap2/usb.h | 5 -
include
-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
drivers/usb/musb/am35x.c | 73
1 file changed, 73 insertions(+)
diff --git a/drivers/usb/musb/am35x.c b/drivers/usb/musb/am35x.c
index c41fe58..3c1477a 100644
--- a/drivers/usb/musb/am35x.c
name declarations
for interface and function clock to the device tree, so the am35x
glue code's clk_get() calls can find them.
Rolf Peukert (5):
Make am35x helper function declarations accessible
Export am35x helper functions
Add device tree support for M-USB on AM35xx SOCs
Use new MUSB device
To be able to call these four helper functions from a M-USB AM35x driver
module, their name symbols need to be exported.
Signed-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
arch/arm/mach-omap2/omap_phy_internal.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach
Use new MUSB device name in AM3517 device tree and add name declarations
for interface and function clock, so the am35x drivers clk_get() calls
can find them.
Signed-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
arch/arm/boot/dts/am3517.dtsi | 4 +++-
1 file changed, 3 insertions
Add some information about the new device name to the DT documentation.
Signed-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 35
++
1 file changed, 35 insertions(+)
diff --git a/Documentation/devicetree/bindings/us
On 09.10.2015 02:54, Ladislav Michl wrote:
> Hi there!
>
> on custom AM37x board running 2.6.37 this was enough to enable gpio 67:
> echo 71 > /sys/class/gpio/export
> echo out > /sys/class/gpio/gpio71/direction
> echo 1 > /sys/class/gpio/gpio71/value
>
> However, with DT configured linux-4.2
succeed.
Signed-off-by: Rolf Peukert <rolf.peuk...@imms.de>
---
drivers/clk/ti/clk-3xxx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/ti/clk-3xxx.c b/drivers/clk/ti/clk-3xxx.c
index 8831e1a..b635deb 100644
--- a/drivers/clk/ti/clk-3xxx.c
+++ b/drivers/clk/ti/clk-
Hi,
we're running a 4.x kernel on a board with an AM3505 CPU and would like
to use device trees. The AM35xx glue code for the M-USB controller
didn't support configuration from a DT yet. I now got it working
somehow, but I'm not sure if I'm doing it the correct way. So this post
is not meant as a
Hi Felipe,
thank you for your reply.
On 07.10.2015 15:59, Felipe Balbi wrote:
>
> Hi,
>
> (please sure you also Cc linux-...@vger.kernel.org for MUSB patches)
>
> Rolf Peukert <rolf.peuk...@imms.de> writes:
[...]
>> b) The M-USB port on our board is w
On 07.10.2015 14:15, kbuild test robot wrote:
> Hi Rolf,
>
> [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please
> ignore]
>
> config: arm-omap2plus_defconfig (attached as .config)
> reproduce:
> wget
>
On 13.10.2015 10:15, Tero Kristo wrote:
> On 10/12/2015 06:22 PM, Rolf Peukert wrote:
>> The glue code in drivers/usb/musb/am35x.c calls clk_get() to get its
>> interface and function clocks for the M-USB controller. These calls fail
>> in the current kernel. This patch a
Hi Felipe,
On 07.10.2015 18:22, Felipe Balbi wrote:
[...]
b) The M-USB port on our board is wired as host only. If a device is
unplugged, the driver normally goes into some idle state and waits for
an ID signal change. But on our board that never happens.
>>>
>>> did you route ID
13 matches
Mail list logo