Originaly, otg driver will call the callbacks in platform data
for PHY initialization and shut down.
With PHY driver, it will call the APIs provided by PHY driver
for PHY initialization and shut down. It removes the callbacks
in platform data, and at same time it removes one block in the
way of ena
for ttc_dkb board, we use phy driver for usb support.
Modify the usb support for udc/otg/ehci support.
Signed-off-by: Chao Xie
---
arch/arm/mach-mmp/ttc_dkb.c | 39 ++-
1 files changed, 30 insertions(+), 9 deletions(-)
diff --git a/arch/arm/mach-mmp/ttc_dkb
The patches create the mv-usb phy driver
The patches remove the callbacks in the platform data for phy
initialization and shutdown, and directly write a phy driver
and make udc/ehci/otg to call it.
usb: phy: protect phy init and shutdown for mutiple deivces
usb: phy: mv_usb2: add PHY driver f
Originaly, udc driver will call the callbacks in platform data
for PHY initialization and shut down.
With PHY driver, it will call the APIs provided by PHY driver
for PHY initialization and shut down. It removes the callbacks
in platform data, and at same time it removes one block in the
way of ena
The phy_init and phy_deinit APIs are removed from the pdata.
Directly get the phy driver and invoke the callbacks of phy
drivers for phy initialization and shutdown.
Signed-off-by: Chao Xie
---
drivers/usb/gadget/mv_u3d.h |3 +-
drivers/usb/gadget/mv_u3d_core.c | 54 ++
The phy initialization code will be done by phy driver.
Signed-off-by: Chao Xie
---
include/linux/platform_data/mv_usb.h |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/include/linux/platform_data/mv_usb.h
b/include/linux/platform_data/mv_usb.h
index 98b7925..b4b5d6f
add the udc/otg/ehci devices for mmp2
Signed-off-by: Chao Xie
---
arch/arm/mach-mmp/include/mach/mmp2.h |4
arch/arm/mach-mmp/mmp2.c |4
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-mmp/include/mach/mmp2.h
b/arch/arm/mach-mmp/includ
We defined new usb devices for usb ehci/udc/otg/phy.
So remove the old definitions.
Signed-off-by: Chao Xie
---
arch/arm/mach-mmp/include/mach/pxa910.h |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-mmp/include/mach/pxa910.h
b/arch/arm/mach-mmp/include/
for brownstone board, add the udc/otg/ehci support
Signed-off-by: Chao Xie
---
arch/arm/mach-mmp/brownstone.c | 56
1 files changed, 56 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-mmp/brownstone.c b/arch/arm/mach-mmp/brownstone.c
index 235
Some USB devices will share same phy, so make the ->init
and ->shutdown to be protected.
Only first device will initialize the phy, and only last device
can shutdown phy.
Signed-off-by: Chao Xie
---
drivers/usb/phy/phy.c |6 ++
include/linux/usb/phy.h | 22 ++
2 f
because phy is seperated from the usb controller driver,
we can use the common pxa_device_desc for device register.
Signed-off-by: Chao Xie
---
arch/arm/mach-mmp/include/mach/pxa910.h |4
arch/arm/mach-mmp/pxa910.c |4
2 files changed, 8 insertions(+), 0 deletions(
Originaly, ehci driver will call the callbacks in platform data
for PHY initialization and shut down.
With PHY driver, it will call the APIs provided by PHY driver
for PHY initialization and shut down. It removes the callbacks
in platform data, and at same time it removes one block in the
way of en
The PHY is seperated from usb controller.
The usb controller used in marvell pxa168/pxa910/mmp2 are same,
but PHY initialization may be different.
the usb controller can support udc/otg/ehci, and for each of
the mode, it need PHY to initialized before use the controller.
Direclty writing the phy dr
This patch add a missing usb device id for the GDMBoost V1.x device
The patch is against 3.9-rc5
Signed-off-by: Stefani Seibold
---
ftdi_sio.c |1 +
ftdi_sio_ids.h |1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
inde
On Sun, Apr 07, 2013 at 02:25:23PM +0800, li.ru...@zte.com.cn wrote:
>
> LINUX KRENEL: next-20130405
> SOURCE CODE PATH:linux-next-refs/tags/next-20130405/drivers/usb/serial/
I don't need these two lines, what are they for?
> Signed-off-by: Rui li
>
> --
Use the appropriate WARN() and WARN_ON() accessors to avoid a build error
when CONFIG_BUG=n:
drivers/usb/gadget/configfs.c: In function 'config_usb_cfg_unlink':
drivers/usb/gadget/configfs.c:442:2: error: implicit declaration of
function '__WARN_printf'
drivers/usb/gadget
On Sat, Apr 6, 2013 at 4:44 PM, Fabio Estevam wrote:
> Maybe bad DDR initialization? Are using U-boot or bootlets to setup the DDR?
>
> What is your DDR frequency: 133 or 96MHz? I saw some posts in the
> olimex forum that people had to run it at 96MHz to get stable
> operation.
Thanks Fabio,
Tha
On Sat, Apr 06, 2013 at 02:35:34AM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 04/05/2013 08:40 PM, Sergei Shtylyov wrote:
>
> >
> >>>Here's the set of 4 patches against the Simon Horman's
> >>>'renesas.git' repo,
> >>>'renesas-next-20130404v2' tag and the 2 Ether patches I've
> >>>reposted
Hi,
>> Now i insmod g_file_storage gadget with file=/mnt/sd/backing_file, the
>> SCSI_READ_10 command is still not working properly.
>
> What makes you think that?
Because the SCSI_READ_10 is able to read the MBR from the backing
file, and after that, SCSI_READ_10 reads all zeroes (fails to read
Hello,
I want to test USB keyboard for XHCI in u-boot and to do that i need the
Interrupt transfer code in XHCI controller driver in u-boot. If
possible, can you help me to give that piece of code or can you help me
to figure out in kernel where can i find it so that i can try to
replicate it in u
Signed-off-by: Huang Rui
---
include/uapi/linux/usb/ch9.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/usb/ch9.h b/include/uapi/linux/usb/ch9.h
index f738e25..aa33fd1 100644
--- a/include/uapi/linux/usb/ch9.h
+++ b/include/uapi/linux/usb/ch9.h
@@ -138
On Mon, Apr 08, 2013 at 09:45:52AM +0530, Puneet Sharma wrote:
> The information contained in this email and any attachments is confidential
> and may be subject to copyright or other intellectual property protection. If
> you are not the intended recipient, you are not authorized to use or discl
22 matches
Mail list logo