The operations in current otg.c are actually for USB PHY's.
Move it from drivers/usb/otg/ to drivers/usb/phy/
Signed-off-by: Peter Chen
---
drivers/usb/otg/Makefile |3 ---
drivers/usb/phy/Makefile |3 +++
drivers/usb/{otg/otg.c => phy/phy.c} |2 +-
3 files ch
Hi Felipe,
Below are two patches to split some phy related things from
otg.
Changes for v2:
- Use git mv / git format -M to create patch for rename otg.c to phy.c
Peter Chen (2):
usb: phy: rename enum usb_otg_state to usb_state
usb: phy: rename otg.c to phy.c
drivers/usb/otg/Makefile
These states are not all otg specific, and they stands for
general usb state.
Signed-off-by: Peter Chen
---
drivers/usb/otg/isp1301_omap.c |4 ++--
drivers/usb/otg/otg.c | 12 +++-
drivers/usb/otg/otg_fsm.c |6 +++---
include/linux/usb/msm_hsusb.h |2 +-
incl
At commit 925aa46ba963a4da6d8ee6ab1d04a02ffa8db62b, Richard Zhao
adds the phy notification callback
when port change occurs. In fact, this phy notification should
be added according to below rules:
1. Only set HW_USBPHY_CTRL.ENHOSTDISCONDETECT
during high speed host mode.
2. Do not set HW_USBPHY_
Changes for v2:
- Add Tested-by: Mike Thompson
At some i.mx SoCs, when controller works at host mode, the PHY
register needs to be changed at device connect, disconnect, bus
suspend and resume due to the SoC limitations.
The phy notification should be added according to below rules:
1. Only se
These notify will be called during the bus suspend/resume procedure.
The mxs-phy needs to set/clear HW_USBPHY_CTRL.ENHOSTDISCONDETECT
during the connect, disconnect,suspend and resume procedure.
The phy notification should be added according to below rules:
1. Only set HW_USBPHY_CTRL.ENHOSTDISCON
This let usb phy driver has the chance to change hw settings during
the controller suspend/resume procedure.
Besides, old parameter "port" is useless for phy notify, as one usb
phy is only for one usb port. New parameter "speed" stands for
the device's speed which is on the port.
Signed-off-by: P
When there is a device at the port, it needs to notify PHY
driver bus's status during bus suspend/resume procedure
for some freescale i.mx SoC (i.mx23, i.mx28, i.mx6).
Signed-off-by: Peter Chen
Tested-by: Mike Thompson
---
Changes for v2:
- Add Tested-by: Mike Thompson
drivers/usb/chipidea/h
Sorry to add others, this patchset only sends to Felipe.
Peter Chen
On Mon, Oct 8, 2012 at 4:18 PM, Peter Chen wrote:
> Hi Felipe,
>
> Below are two patches to split some phy related things from
> otg.
>
> Changes for v2:
> - Use git mv / git format -M to create patch for rename otg.c to phy.c
>
Used of_platform_populate() to populate dwc3 core platform_device
from device tree data. Since now the allocation of unique device id is
handled be of_*, removed the call to dwc3_get_device_id.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/dwc3-omap.c | 52
Used device_for_each_child() to handle child device (dwc3 core) removal
during devexit of dwc3 omap.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/dwc3-omap.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drivers/u
Includes few minor fixes in dwc3-omap like populating the compatible
string in a correct way, extracting the utmi-mode property properly and
changing the index of get_irq since irq of core is removed from hwmod
entry.
Also updated the documentation with dwc3-omap device tree binding
information.
S
The runtime API's takes care of setting the SYSCONFIG register with
appropriate values. Hence explicit writes to SYSCONFIG register is
removed.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/dwc3-omap.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/
Added dwc3 support for dwc3 core and update the documentation with
device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/dwc3.txt | 23 +++
drivers/usb/dwc3/core.c| 14 --
2 fil
Add an API in the omap glue layer to write to the mailbox register which
can be used by comparator driver(twl). To pass the detection of the attached
device (signified by VBUS, ID) to the dwc3 core, dwc3 core has to write
to the mailbox regiter.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/
Before accessing any register, runtime API's should be invoked to enable
the clocks. runtime API's are added here to prevent abort during register
access.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/dwc3-omap.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/driv
This patch series adds dt support to dwc3 core and fixes few minor
stuff in dwc3-omap glue to get dwc3 working.
While at that it also uses *of_platform* to create the child device
(dwc3-core) and fixes to use runtime API's to enable clock and write
to SYSCONFIG register.
Changes from v2:
* Fixed
Hi Constantine,
On 10/4/2012 9:52 PM, Constantine Shulyupin wrote:
> From: Constantine Shulyupin
>
> Signed-off-by: Constantine Shulyupin
> ---
>
> Note:
>
> USBPHY_CTL_PADDR and USBPHY_CLKFREQ_24MHZ are defined in board-dm365-evm.c
> because davinci.h can't be included from drivers/usb/musb
Hi all,
This patch series contains EHCI and OHCI platform drivers conversions,
allowing quite some EHCI and OHCI platform drivers to be deleted.
While converting, Alan Stern asked me to fold some cleanups and fixes in the
EHCI and OHCI platform drivers, these changes have now been addressed.
Cha
This driver is not registered by any in-tree users, and if really needed by
some out of tree user, the same functionnality can be restored using the
ohci-platform driver using the following platform_data parameters:
big_endian_desc = 1
big_endian_mmio = 1
no_big_frame_no = 1
The platform code has been migrated to register the ehci-platform driver, thus
obsoleting the ehci-xls driver, which can be removed.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- reworded commit message
drivers/us
Merge ohci_finish_controller_resume with ohci_resume as suggested by Alan
Stern. Since ohci_finish_controller_resume no longer exists, update the
various OHCI drivers to call ohci_resume() instead. Some drivers used to set
themselves the bit HCD_FLAG_HW_ACCESSIBLE, which is now handled by
ohci_resu
This patch modifies the ohci platform driver to accept the num_ports
parameter to be set via platform_data. Setting the number of ports must be
done after the call to ohci_hcd_init().
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
Changes in v3:
- imp
The users have been converted to use the ehci platform driver instead, thus
making the ehci-cns3xxx driver obsolete, so remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v2 and v3
Changes in v1:
- only remove the corresponding c
This patch makes all SuperH boards using the ohci-sh platform driver to use
the ohci-platform driver instead, which is suitable for use by these boards.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
Changes in v3:
- improved commit message
No change
All users have been converted to use the OHCI platform driver instead, thus
making ohci-sh obsolete, so remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v2 and v3
drivers/usb/host/Kconfig|6 +-
drivers/usb/host/ohci-hc
Convert the Alchemy platform to register the ohci-platform driver, now that
the ohci-platform driver properly handles the specific ohci-au1xxx resume
from suspend case.
This also greatly simplifies the power_{on,off} callbacks and make them
work on platform device id instead of checking the OHCI c
All users have been converted to use the OHCI platform driver instead, thus
making ohci-au1xxx obsolete, remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- rebased on top of the latest OHCI HCD changes
drive
This patch changes the ehci-platform driver to use the device managed helper
function for requesting memory region and ioremapping memory resources.
As a result the error path in the probe function is simplified, and the
platform driver remove callback does no longer need to release and iounmap
mem
We meant to write "resource" instead of "recourse", this patch fixes this
typo.
Signed-off-by: Florian Fainelli
---
Changes in v2:
- rebased against greg's latest usb-next
drivers/usb/host/ohci-platform.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/oh
Fix the obvious typo in the error message, we meant to write "resource"
instead of "recourse".
Signed-off-by: Florian Fainelli
---
Changes in v2:
- rebased against greg's latest usb-next
drivers/usb/host/ehci-platform.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driv
This patch converts the ohci-platform driver to use dev_err() functions
instead of pr_err().
Signed-off-by: Florian Fainelli
---
Changes since v2:
- rebased against greg's latest usb-next
drivers/usb/host/ohci-platform.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
This patch changes the ohci-platform driver to use the device managed helper
function for requesting memory region and ioremapping memory resources.
As a result the error path in the probe function is simplified, and the
platform driver remove callback does no longer need to release and iounmap
mem
This patch converts the ehci-platform driver to make use of the dev_err()
functions instead of pr_err().
Signed-off-by: Florian Fainelli
---
Changes in v2:
- rebased against greg's latest usb-next
drivers/usb/host/ehci-platform.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
d
A previous patch converted the Alchemy platform to use the OHCI and EHCI
platform drivers. As a result, all the common logic to handle USB present in
drivers/usb/host/alchemy-common.c has no reason to remain here, so we move it
to arch/mips/alchemy/common/usb.c which is a more appropriate place. Th
From: Constantine Shulyupin
Remove USB configuration in arch/arm/mach-davinci/usb.c accordingly
CONFIG_USB_MUSB_OTG CONFIG_USB_MUSB_PERIPHERAL CONFIG_USB_MUSB_HOST
and set MUSB_OTG configuration by default
because this configuration options are removed from Kconfig.
Signed-off-by: Constantine
This driver is not registered by any in-tree user. If needed it the EHCI
driver can be reinstatied using the ehci-platform driver with caps_offset to
0x100.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- slightly rew
The Loongson 1B EHCI driver does nothing more than what the EHCI platform
driver already does, so use the generic implementation.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes since v1
arch/mips/configs/ls1b_defconfig |1 +
arch
The EHCI platform driver is suitable for use by the Netlogic XLR platform
since there is nothing specific that the EHCI XLR platform driver does.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- really change driver nam
Use the ehci platform driver power_{on,suspend,off} callbacks to perform the
USB block gate enabling/disabling as what the ehci-au1xxx.c driver does.
Update the db1200 and db1300 defconfigs to now select the EHCI platform
driver.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased agains
The platform code has been converted to use the ehci-platform driver instead
thus obsoleting the ehci-au1xxx driver, which can be removed.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- reworded commit message
driv
Change the PNX8550 platform code to register an ohci-platform driver instead
of ohci-pnx8550 since the ohci-platform is suitable for use.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v2 and v3
arch/mips/pnx8550/common/platform.c |
As suggested by Alan Stern, the code checking for the OHCI RH already
suspended is no longer required since the bug it fixes has not been seen in
ages. Remove that check making ohci_suspend much simpler.
Signed-off-by: Florian Fainelli
---
Changes in v3:
- rebased against greg's latest usb-next
As suggested by Alan Stern, move the ohci-pci.c ohci_pci_{suspend,resume}
routines to ohci-hcd.c. Due to their move, also rename them to
ohci_{suspend,resume} to make it clear they operate on ohci_hcd. Since they
are not necessarily called, annotate them with __maybe_unused, and make them
enclosed
All users have been converted to use the OHCI platform driver instead, thus
making ohci-xls obsolete, remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- reworded commit message
drivers/usb/host/ohci-hcd.c |
The OHCI platform driver is suitable for use by the Netlogic XLR platform
so use this driver instead of the OHCI XLS platform driver.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- really make the code register the "
All users have been converted to use the OHCI platform driver instead, thus
making ohci-cns3xxx, so remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
Changes in v2:
- reworded commit message
drivers/usb/host/Kconfig
This patch converts the cns3xxx platform to use the ohci-platform driver which
is now suitable for use.
A previous patch converted the cns3xxx platform to use the ehci-platform
driver, and thus introduced the need to have power_{on,off} callbacks.
Since both the EHCI and OHCI platform drivers use
The users have been converted to use the platform OHCI driver instead, thus
making the ohci-pnx8550 driver obsolete, so remove it.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v2 and v3
drivers/usb/host/ohci-hcd.c |5 -
drive
This patch converts the cns3xxx platform to use the ehci-platform driver
instead of the ehci-cns3xxx platform driver.
The ehci-platform driver is provided with power_{on,off} callbacks to ensure
proper block gating and USB configuration of the EHCI controller.
Signed-off-by: Florian Fainelli
---
Enhance the ehci-platform driver to also accept no_io_watchdog as a platform
data parameter. When no_io_watchdog is set to 1, the ehci controller will set
ehci->need_io_watchdog to 0. Since most EHCI controllers do need the I/O
watchdog to be on, only let those which need it to turn the watchdog of
The platform code registering the Loongson 1B EHCI driver has now been
converted to register the ehci-platform driver instead, thus obsoleting the
ehci-ls1x driver, which can be removed.
Signed-off-by: Florian Fainelli
---
Changes in v4:
- rebased against greg's latest usb-next
No changes in v3
On Mon, Oct 08, 2012 at 03:11:19PM +0200, Florian Fainelli wrote:
> The EHCI platform driver is suitable for use by the Netlogic XLR platform
> since there is nothing specific that the EHCI XLR platform driver does.
>
> Signed-off-by: Florian Fainelli
> ---
> Changes in v4:
> - rebased against gr
This patchset is based on the work by Praveen Paneri for
samsung-usbphy driver:
http://comments.gmane.org/gmane.linux.kernel.samsung-soc/12653
Tested on smdk5250 target with usb-next branch along with
arch patches for exynos5250:
http://thread.gmane.org/gmane.linux.kernel.samsung-soc/13042
http://
This patch adds host phy support for samsung's exynos5250.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/Kconfig |1 -
drivers/usb/phy/samsung-usbphy.c | 362 --
include/linux/platform_data/samsung-usbphy.h |9 +-
3 files change
It adds 'type' argument to pmu_isolation function, aligning
with other platforms, which keeps track of usbphy_type.
Signed-off-by: Vivek Gautam
---
arch/arm/mach-s3c64xx/setup-usb-phy.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-s3c64xx/setup-usb-phy.
Adding usbphy node for Exynos5250 along with the platform data.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 12 -
arch/arm/boot/dts/exynos5250.dtsi |5 ++
arch/arm/mach-exynos/Kconfig |1 +
arch/arm/mac
Adding the transceiver to ehci driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ehci-s5p.c | 62 +-
1 files changed, 43 insertions(+), 19 deletions(-)
d
Adding the transceiver to ohci driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
---
drivers/usb/host/ohci-exynos.c | 62 +++
1 files changed, 43 insertions(+), 19 deletions(-)
d
On Mon, 8 Oct 2012, Tony Prisk wrote:
> My biggest concern about the binding is all the platform_data that is
> used in the ehci-platform driver that I don't recognise.
> arch-vt8500 doesn't require any of them.
>
> Looking through, most seem like they would be obvious candidates for DT
> propert
On Mon, 8 Oct 2012, Peter Chen wrote:
> At commit 925aa46ba963a4da6d8ee6ab1d04a02ffa8db62b, Richard Zhao
> adds the phy notification callback
> when port change occurs. In fact, this phy notification should
> be added according to below rules:
>
> 1. Only set HW_USBPHY_CTRL.ENHOSTDISCONDETECT
>
On Mon, 8 Oct 2012, Florian Fainelli wrote:
> Hi all,
>
> This patch series contains EHCI and OHCI platform drivers conversions,
> allowing quite some EHCI and OHCI platform drivers to be deleted.
>
> While converting, Alan Stern asked me to fold some cleanups and fixes in the
> EHCI and OHCI pl
On Monday 08 October 2012 11:58:35 Alan Stern wrote:
> On Mon, 8 Oct 2012, Florian Fainelli wrote:
>
> > Hi all,
> >
> > This patch series contains EHCI and OHCI platform drivers conversions,
> > allowing quite some EHCI and OHCI platform drivers to be deleted.
> >
> > While converting, Alan Ste
* Philippe De Swert [121004 10:00]:
> This patch is based on the discussion of a previous patch to fix an issue
> where the omap2430 musb driver is not working for N9/N950.
>
> Moving all the interrupt handling to the devices. Avoids inclusion of generic
> interrupt and breakage due to sometimes
On Mon, Oct 08, 2012 at 07:08:39PM +0200, Markus Schauler wrote:
> Hi,
>
> my garmin device is crashing my new 3.6.1 kernel...
> How can I help huntig the bug ?
Did this work properly with 3.6.0? 3.5.0? If so, any chance you can
run 'git bisect' to track this down to the commit that caused the
Yo All!
I reported last month that when I plug a USB 1.1 or USB 2.0 device into
my Etron USB 3.0 controller (xHCI) the device will not work. The
failure message is always:
[ 28.338599] usb 8-2.4: Not enough bandwidth for new device state.
[ 28.338613] usb 8-2.4: can't set config #1, error -2
Here are some Link PM patches. I wanted to put them out for review
before I send them off to Greg.
The first patch allows LPM to remain enabled after a driver fails a
probe. If libusual was compiled into the kernel, without this patch,
LPM would remain disabled after libusual loaded for USB 3.0
Before a driver is probed, we want to disable USB 3.0 Link Power
Management (LPM), in case the driver needs hub-initiated LPM disabled.
After the probe finishes, we want to attempt to re-enable LPM, order to
balance the LPM ref count.
When a probe fails (such as when libusual doesn't want to bind
Some USB 3.0 devices signal that they don't implement Link PM by having
all zeroes in the U1/U2 exit latencies in their SuperSpeed BOS
descriptor. Don found that a Western Digital device he has experiences
transfer errors when LPM is enabled. The lsusb shows the U1/U2 exit
latencies are set to ze
The Set SEL control transfer tells a device the exit latencies
associated with a device-initated U1 or U2 exit. Since a parent hub may
initiate a transition to U1 soon after a downstream port's U1 timeout is
set, we need to make sure the device receives the Set SEL transfer
before the parent hub t
SEL and PEL are in microseconds, not milliseconds. Also, fix a split
string that will trigger checkpatch warnings.
Signed-off-by: Sarah Sharp
---
drivers/usb/core/hub.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
ind
On Mon, 8 Oct 2012, Markus Schauler wrote:
> Hi,
>
> my garmin device is crashing my new 3.6.1 kernel...
> How can I help huntig the bug ?
It looks like the problem is that the garmin-gps driver uses the wrong
callbacks for creating and destroying ports. The patch below should
help. Let me k
On Mon, 8 Oct 2012, Sarah Sharp wrote:
> Some USB 3.0 devices signal that they don't implement Link PM by having
> all zeroes in the U1/U2 exit latencies in their SuperSpeed BOS
> descriptor. Don found that a Western Digital device he has experiences
> transfer errors when LPM is enabled. The ls
On Mon, 8 Oct 2012, Sarah Sharp wrote:
> The Set SEL control transfer tells a device the exit latencies
> associated with a device-initated U1 or U2 exit. Since a parent hub may
> initiate a transition to U1 soon after a downstream port's U1 timeout is
> set, we need to make sure the device recei
Hi,
I have noticed this mailing list has been intensively used to discuss
patch development discussion. So please let me know if I should move
my question to more appropriate places.
In order to experiment something I need to pretend that my phone has a
super fast SD card (faster than what is ava
On Sat, Oct 06, 2012 at 12:53:43PM +0800, loody wrote:
> hi sarah:
>
> 2012/10/6 Sarah Sharp :
> > I see. Is there a particular reason why the current Linux xHCI driver
> > doesn't meet your needs? Like maybe your host isn't PCI based? I'm
> > confused as to why you would need to understand the
杨苏立 Yang Su Li wrote:
> In order to experiment something I need to pretend that my phone has a
> super fast SD card (faster than what is available in the market). So I
> want to simulate it through desktop ramdisk (which is basically disk
> in memory). And here is basically my plan:
>
> 1. Get an
Convert USB descriptor's fields to CPU byte order before using locally in USB
NCM gadget driver.
Tested on MIPS32 big-endian device.
Signed-off-by: Dmytro Milinevskyy
---
drivers/usb/gadget/f_ncm.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/gadget
On Mon, Oct 08, 2012 at 12:25:48PM -0700, Gary E. Miller wrote:
> Yo All!
>
> I reported last month that when I plug a USB 1.1 or USB 2.0 device into
> my Etron USB 3.0 controller (xHCI) the device will not work. The
> failure message is always:
>
> [ 28.338599] usb 8-2.4: Not enough bandwidth
On Mon, Oct 08, 2012 at 04:03:01PM -0400, Alan Stern wrote:
> On Mon, 8 Oct 2012, Sarah Sharp wrote:
>
> > Some USB 3.0 devices signal that they don't implement Link PM by having
> > all zeroes in the U1/U2 exit latencies in their SuperSpeed BOS
> > descriptor. Don found that a Western Digital de
On Mon, 8 Oct 2012, 杨苏立 Yang Su Li wrote:
> Hi,
>
> I have noticed this mailing list has been intensively used to discuss
> patch development discussion. So please let me know if I should move
> my question to more appropriate places.
>
> In order to experiment something I need to pretend that m
Meanwhile, after many re-compliles:
0998d0631001288a5974afc0b2a5f568bcdecb4d is the first bad commit
commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
Author: Hans de Goede
Date: Wed May 23 00:09:34 2012 +0200
device-core: Ensure drvdata = NULL when no driver is bound
1) drvdata is for
Yo Sarah!
On Mon, 8 Oct 2012 14:09:37 -0700
Sarah Sharp wrote:
> > Any new ideas?
>
> Have you tried to see if there's a firmware update for your Etron host
> controller?
www.etron.com is down. I have the latest mobo BIOS.
> The error you're getting seems to me to indicate a
> hardware issue
commit 3735ba8db8e6ea22ad3ff524328926d8d780a884 "powerpc/usb: fix bug of
CPU hang when missing USB PHY clock" introduced a new build warning:
In file included from linux/drivers/usb/host/ehci-hcd.c:1208:0:
linux/drivers/usb/host/ehci-fsl.c: In function 'ehci_fsl_setup_phy':
linux/drivers/usb/host/
Hi,
Thanks a lot for the detailed and insightful answer. That's exactly
what I am looking for.
I do have some comments/further questions inline though.
Suli
On Mon, Oct 8, 2012 at 4:02 PM, Peter Stuge wrote:
> 杨苏立 Yang Su Li wrote:
>> In order to experiment something I need to pretend that my
I hope I could do that too.
However I imagine it will be hard to get a compatible memory card with
is, say, 16GB/32GB, and insert it into a main stream phone. Or is my
assumption wrong here?
Thanks.
Suli
On Mon, Oct 8, 2012 at 4:28 PM, Alan Stern wrote:
> On Mon, 8 Oct 2012, 杨苏立 Yang Su Li wro
On Mon, Oct 08, 2012 at 04:05:00PM -0400, Alan Stern wrote:
> On Mon, 8 Oct 2012, Sarah Sharp wrote:
>
> > The Set SEL control transfer tells a device the exit latencies
> > associated with a device-initated U1 or U2 exit. Since a parent hub may
> > initiate a transition to U1 soon after a downst
杨苏立 Yang Su Li wrote:
> is there some hardware I can by to turn my desktop into an USB
> device or USB OTG device? Preferably this hardware should use my
> desktop's memory to back-up its storage.
Not that I know of.
> > If the USB OTG host has a Micro-AB connector then yes, this cable is
> > ne
hi, Daniel
my usb 3.0 hard drive doesn't have external power. this is a "western
digital" usb hard drive: WDBACY5000AWT
here is a Product Specifications:
http://www.wdc.com/wdproducts/library/AAG/ENG/4178-705131.pdf
i start my laptop with ubuntu, the usb3.0 port could use the usb3.0
hard drive. bu
On Tue, 9 Oct 2012, Peter Stuge wrote:
> 杨苏立 Yang Su Li wrote:
> > is there some hardware I can by to turn my desktop into an USB
> > device or USB OTG device? Preferably this hardware should use my
> > desktop's memory to back-up its storage.
>
> Not that I know of.
There are ways to do this.
Hi,
Thanks again. I really appreciate your prompt and insightful answers.
And again, my comments are inline :)
Suli
On Mon, Oct 8, 2012 at 7:04 PM, Peter Stuge wrote:
> 杨苏立 Yang Su Li wrote:
>> is there some hardware I can by to turn my desktop into an USB
>> device or USB OTG device? Preferab
Alan Stern wrote:
> > > is there some hardware I can by to turn my desktop into an USB
> > > device or USB OTG device? Preferably this hardware should use my
> > > desktop's memory to back-up its storage.
> >
> > Not that I know of.
>
> Linux supports the net2272 and net2280 boards.
I'm not sure
杨苏立 Yang Su Li wrote:
> Connecting an SSD to a cell phone is actually my initial idea. I
> wanna try memory/ramdisk because I need fine control over the I/O
> speed I get. As memory is a true random access device,
Even DRAM isn't completely random access, but memory controllers do
a good job at fa
Hi,
On Monday 08 October 2012 07:42 PM, Vivek Gautam wrote:
It adds 'type' argument to pmu_isolation function, aligning
with other platforms, which keeps track of usbphy_type.
Signed-off-by: Vivek Gautam
---
arch/arm/mach-s3c64xx/setup-usb-phy.c |2 +-
1 files changed, 1 insertions(+),
>
> Simply reading this patch shows that it contains at least two errors.
Thanks for review.
>
> > @@ -4187,6 +4190,10 @@ static void hub_port_connect_change(struct
> usb_hub *hub, int port1,
> > }
> > }
> >
> > + if (hcd->phy && !hdev->parent &&
> > + !(portstatus
On Tue, Oct 9, 2012 at 2:06 AM, 杨苏立 Yang Su Li wrote:
> Hi,
>
> I have noticed this mailing list has been intensively used to discuss
> patch development discussion. So please let me know if I should move
> my question to more appropriate places.
>
> In order to experiment something I need to pret
96 matches
Mail list logo
