Hi,
> >
> > Yes, the devices /dev/mmcblk0 and /dev/mmcblk0p1 exist. The
> > /dev/mmcblk0 can be mounted. The dmesg does not contain other
> > messages. I am not sure the way to use g_file_storage.ko with UDC.
Please
> kindly help me.
> >
> > # ls /dev/mmc*
> > /dev/mmc0 /dev/mmc2 /dev/
On 12/11/2012 02:37 PM, Alan Stern wrote:
On Tue, 11 Dec 2012, prasannatsmkumar wrote:
Hi All,
I connected an Android phone using USB cable to my machine running
Linux (Linux 3.0, 3.2, 3.5). Mounted the SD card in phone in system
(phone is just a pass through I guess). When I choose "Safely Re
On Wed, Dec 12, 2012 at 10:34 AM, Andrew Lutomirski wrote:
> On Tue, Dec 11, 2012 at 6:32 PM, Huang Ying wrote:
>> On Fri, 2012-12-07 at 22:00 +0100, Rafael J. Wysocki wrote:
>>> On Thursday, December 06, 2012 04:28:08 PM Sarah Sharp wrote:
>>> > On Thu, Dec 06, 2012 at 01:43:32AM +0100, Rafael J
On Tue, Dec 11, 2012 at 6:32 PM, Huang Ying wrote:
> On Fri, 2012-12-07 at 22:00 +0100, Rafael J. Wysocki wrote:
>> On Thursday, December 06, 2012 04:28:08 PM Sarah Sharp wrote:
>> > On Thu, Dec 06, 2012 at 01:43:32AM +0100, Rafael J. Wysocki wrote:
>> > > On Wednesday, December 05, 2012 04:33:44
On Fri, 2012-12-07 at 22:00 +0100, Rafael J. Wysocki wrote:
> On Thursday, December 06, 2012 04:28:08 PM Sarah Sharp wrote:
> > On Thu, Dec 06, 2012 at 01:43:32AM +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, December 05, 2012 04:33:44 PM Sarah Sharp wrote:
> > > > Wakeup from D3 works fine o
On Mon, Dec 10, 2012 at 03:17:34PM +0100, Andrzej Pietrasiewicz wrote:
> @Joel in particular: please see my comment in the bottom.
> I forgot to mention, representing udcs (USB Device Controllers) in
> configfs is similar to interfaces/endpoints: the user needs to guess
> what name to use in mkd
Hi Alan,
I'm finally revisiting the issue with active transfers when a device
disconnects. I'm trying to refresh my memory of the issue.
On Thu, Oct 18, 2012 at 03:54:06PM -0400, Alan Stern wrote:
> Unfortunately the trace isn't termendously helpful. It shows a bunch
> of reads with a few write
On 12/11/2012 11:24 PM, Alan Stern wrote:
On Tue, 11 Dec 2012, Timur wrote:
I am talking about both devices loosing external power at the same time.
Losing external power is different from losing power.
I'm trying to be as precise as I can.
The N7 will then switch to it's internal battery.
Hi Tilman,
Another option is to find and use fx2lib. It includes fx1 based stuff
and should give you some ideas on how to at least make something work.
It uses the open source SDCC compiler, so if you are using something
else some of the syntax is different.
Regards, Steve
On Tue, Dec 11, 2012 a
Peter Stuge writes:
> Tilman wrote:
> What device is that? Is it a Cypress FX2 or an SiLabs C8051?
ezusb (Cypress AN2131)
> > The urb eventually times out. Via debug FS I can see that the urb is
> > indeed submitted. I suspect the firmware to be responsible for this.
>
> That's quite likely.
On Tue, 11 Dec 2012, Timur wrote:
> I am talking about both devices loosing external power at the same time.
Losing external power is different from losing power.
> The N7 will then switch to it's internal battery.
Right. It will continue running, because the battery continues to
supply powe
On 12/11/2012 08:13 PM, Alan Stern wrote:
On Tue, 11 Dec 2012, Timur wrote:
Thank you for your response. Yes, unplugging helps. But host and slave
should also function in a fixed installation setup, where cables are
hidden. I tried different slave devices and they are all "not
accepting address
Am 11.12.2012 17:48, schrieb Alan Stern:
[snip]
>
> We really need to know which component is bad: the host controller or
> the device.
It happens with all USB 1.1 devices I have (several mice and a HP
Deskjet 960c printer).
The same devices do not cause other machines to wake up, so I assume
it
On Thu, Nov 08, 2012 at 01:57:04PM -0800, Sarah Sharp wrote:
> The math in the link status reporting is wrong. The link state is in
> bits 8:5 of the hub port status word, which is split across a char
> array. Currently, if the link state is 0xb (Loopback mode), the status
> char array will look
On Mon, Dec 10, 2012 at 12:57:02PM +0100, Andrzej Pietrasiewicz wrote:
> Hello Joel,
>
> So you are alive, I'm glad to hear from you ;) Thank you for your response.
Yeah, sorry for missing the thread for so long.
> On Saturday, December 08, 2012 12:18 AM Joel Becker wrote:
> > Subject: R
On Tue, Dec 11, 2012 at 03:26:29PM -0500, Alan Stern wrote:
> On Tue, 11 Dec 2012, Alan Stern wrote:
>
> > Overall it looks good and ready for mergin. There is one odd thing
> > about the last patch; I'll send a separate email about it.
>
> Looking at it a second time, I realized there was noth
On Tue, 11 Dec 2012, prasannatsmkumar wrote:
> Hi All,
>
> I connected an Android phone using USB cable to my machine running
> Linux (Linux 3.0, 3.2, 3.5). Mounted the SD card in phone in system
> (phone is just a pass through I guess). When I choose "Safely Remove"
> option in nautilus file man
On Tue, 11 Dec 2012, Alan Stern wrote:
> Overall it looks good and ready for mergin. There is one odd thing
> about the last patch; I'll send a separate email about it.
Looking at it a second time, I realized there was nothing wrong -- I
had simply misunderstood the code.
> Aside from that, f
On Tue, 11 Dec 2012, Sarah Sharp wrote:
> Changelog from v2:
>
> - Added two new patches to the end. One refactors hub_port_wait_reset
>(as Alan requested) and the other converts hub.c to use the new macro
>to set a port link state.
>
> - Patch 5 "USB: Ignore port state until reset co
The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:
Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.8-rc1
for you to fetch changes up to fb37ef98015f864d22be22
On Tue, Dec 11, 2012 at 11:06:59AM -0800, rh wrote:
> On Tue, 11 Dec 2012 10:05:12 -0800
> Greg KH
> wrote:
>
> > On Tue, Dec 11, 2012 at 09:44:36AM -0800, rh wrote:
> > > I am curious to know if there are any rules applied to the text of
> > > tristate in Kconfig. For example what's preferred in
On Tue, 11 Dec 2012, Timur wrote:
> > Thank you for your response. Yes, unplugging helps. But host and slave
> > should also function in a fixed installation setup, where cables are
> > hidden. I tried different slave devices and they are all "not
> > accepting address xx, error -71" after powe
On 12/11/2012 06:36 PM, Timur wrote:
On 12/11/2012 04:34 PM, Alan Stern wrote:
On Mon, 10 Dec 2012, Timur wrote:
N7 is not using a vanilla kernel. It is one thing to apply
modifications
to the given code base. It would be far more difficult (I think) to
replace the kernel as a whole. Maybe I
The USB core hub thread (khubd) is designed with external USB hubs in
mind. It expects that if a port status change bit is set, the hub will
continue to send a notification through the hub status data transfer.
Basically, it expects hub notifications to be level-triggered.
The xHCI host controlle
Changelog from v2:
- Added two new patches to the end. One refactors hub_port_wait_reset
(as Alan requested) and the other converts hub.c to use the new macro
to set a port link state.
- Patch 5 "USB: Ignore port state until reset completes." now removes
several redundant checks for U
When a hot reset fails on a USB 3.0 port, the current port reset code
recursively calls hub_port_reset inside hub_port_wait_reset. This isn't
ideal, since we should avoid recursive calls in the kernel, and it also
doesn't allow us to issue multiple warm resets on reset failures.
Rip out the recur
When the USB core finishes reseting a USB device, the xHCI driver sends
a Reset Device command to the host. The xHC then updates its internal
representation of the USB device to the 'Default' device state. If the
device was already in the Default state, the xHC will complete the
command with an e
If hot and warm reset fails, or a port remains in the Compliance Mode,
the USB core needs to be able to disable a USB 3.0 port. Unlike USB 2.0
ports, once the port is placed into the Disabled link state, it will not
report any new device connects. To get device connect notifications, we
need to p
Refactor hub_port_wait_reset into a small loop to wait for the port
reset to be complete, and then a larger block to deal with the final
port status. This patch should not change any current behavior.
Signed-off-by: Sarah Sharp
---
drivers/usb/core/hub.c | 73 -
The EHCI host controller needs to prevent EHCI initialization when the
UHCI or OHCI companion controller is in the middle of a port reset. It
uses ehci_cf_port_reset_rwsem to do this. USB 3.0 hubs can't be under
an EHCI host controller, so it makes no sense to down the semaphore for
USB 3.0 hubs.
USB 3.0 hubs and roothubs will automatically transition a failed hot
reset to a warm (BH) reset. In that case, the warm reset change bit
will be set, and the link state change bit may also be set. Change
hub_port_finish_reset to unconditionally clear those change bits for USB
3.0 hubs. If these
Change the code that manually issues a Set Port Feature(Link State) to
use the new helper function hub_set_port_link_state().
Signed-off-by: Sarah Sharp
---
drivers/usb/core/hub.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/core/hub.c b/drivers/usb
A USB 3.0 device can transition to the Inactive state if a U1 or U2 exit
transition fails. The current code in hub_events simply issues a warm
reset, but does not call any pre-reset or post-reset driver methods (or
unbind/rebind drivers without them). Therefore the drivers won't know
their device
The next patch will refactor the hub port code to rip out the recursive
call to hub_port_reset on a failed hot reset. In preparation for that,
make sure all code paths can deal with being called with a NULL udev.
The usb_device will not be valid if warm reset was issued because a port
transitioned
An empty port can transition to either Inactive or Compliance Mode if a
newly connected USB 3.0 device fails to link train. In that case, we
issue a warm reset. Some devices, such as John's Roseweil eusb3
enclosure, slip back into Compliance Mode after the warm reset.
The current warm reset code
The port reset code bails out early if the current connect status is
cleared (device disconnected). If we're issuing a hot reset, it may
also look at the link state before the reset is finished.
Section 10.14.2.6 of the USB 3.0 spec says that when a port enters the
Error state or Resetting state,
John's NEC 0.96 xHCI host controller needs a longer timeout for a warm
reset to complete. The logs show it takes 650ms to complete the warm
reset, so extend the hub reset timeout to 800ms to be on the safe side.
This commit should be backported to kernels as old as 3.2, that contain
the commit 75
On Tue, Dec 11, 2012 at 09:44:36AM -0800, rh wrote:
> I am curious to know if there are any rules applied to the text of tristate in
> Kconfig. For example what's preferred in tristate text, the name that a user
> would know because it's printed on the outside of the device or that name
> of the ch
Add device driver for USB2CAN interface from "8 devices"
(http://www.8devices.com).
changes since v5:
* unlock mutex on error
changes since v4:
* removed FSF address
* renamed struct usb_8dev
* removed unused variable free_slots
* replaced some _to_cpu functions with pointer equivalent
* fix ret
On Mon, 10 Dec 2012, Piergiorgio Sartor wrote:
> It might be useful.
> I tried quickly to put 5 instead of 20, but still
> the issue was difficult to reproduce (3.7.0-rc4+).
> It happened (again) only after I increased the CPU
> (or I/O) load by "make -j5" in "/usr/src/linux".
> And even not immed
On 12/11/2012 04:34 PM, Alan Stern wrote:
On Mon, 10 Dec 2012, Timur wrote:
N7 is not using a vanilla kernel. It is one thing to apply modifications
to the given code base. It would be far more difficult (I think) to
replace the kernel as a whole. Maybe I should back port just as little
code as
On Tue, Dec 11, 2012 at 01:29:19AM +0100, Timur wrote:
> On 12/11/2012 12:04 AM, Greg KH wrote:
> >On Mon, Dec 10, 2012 at 11:53:27PM +0100, Timur wrote:
> >>
> >>N7 is not using a vanilla kernel.
> >Yes, I know that quite well :)
> >
> >>It is one thing to apply
> >>modifications to the given code
On Tue, Dec 11, 2012 at 11:51:40AM -0500, Alan Stern wrote:
> On Tue, 11 Dec 2012, Peter Stuge wrote:
>
> > victor wrote:
> > > > please remove these sort of footers when you send emails to a public
> > > > mailing list ;-)
> > >
> > > The footer is auto-inserted by the company email system. I am
On Tue, 11 Dec 2012, fangxiaozhi 00110321 wrote:
> From: fangxiaozhi
>
> To optimize the match rules for the Huawei USB storage devices. Avoid to load
> USB storage driver for modem interface with Huawei devices.
>
> Signed-off-by: fangxiaozhi
>
>
On Tue, 11 Dec 2012, Peter Stuge wrote:
> victor wrote:
> > > please remove these sort of footers when you send emails to a public
> > > mailing list ;-)
> >
> > The footer is auto-inserted by the company email system. I am sorry
> > about it.
>
> Talk to your company about how it is impossible
On Tue, 11 Dec 2012, Lan Tianyu wrote:
> Hi Alan&Greg:
> Since 3.1, Alan enabled usb device wakeup default, there are
> a lot of problem that immediately resume when enter into s2ram/s2disk.
> I have traced some these bugs. Most of these bugs are related usb1.1
> device which attached to
On Tue, 11 Dec 2012, Lan Tianyu wrote:
> >> @@ -108,11 +109,14 @@ MODULE_PARM_DESC(use_both_schemes,
> >> DECLARE_RWSEM(ehci_cf_port_reset_rwsem);
> >> EXPORT_SYMBOL_GPL(ehci_cf_port_reset_rwsem);
> >>
> >> +#define HUB_PORT_RECONNECT_TRIES 20
> >
> > 20 is an awful lot. Do you really need an
On Mon, 2012-12-10 at 15:15 -0800, United Seabears Corp. wrote:
> Two months ago I asked for
> assistance with the installation of a Franklin U600 3G/4G modem on the
> above OS. Meanwhile I managed to get the 3G part of the dual modem to
> work reliably.
> I had to discover on my own that this m
On Tue, 2012-12-11 at 15:26 +, Steve Glendinning wrote:
> This patch enables USB dynamic autosuspend for LAN9500A. This
> saves very little power in itself, but it allows power saving
> in upstream hubs/hosts.
[]> diff --git a/drivers/net/usb/smsc95xx.c b/drivers/net/usb/smsc95xx.c
[]
> +
victor wrote:
> > please remove these sort of footers when you send emails to a public
> > mailing list ;-)
>
> The footer is auto-inserted by the company email system. I am sorry
> about it.
Talk to your company about how it is impossible for you to contribute
to an open source project on a pub
On Tue, Dec 11, 2012 at 11:26 PM, Steve Glendinning
wrote:
> This patch enables USB dynamic autosuspend for LAN9500A. This
> saves very little power in itself, but it allows power saving
> in upstream hubs/hosts.
>
> The earlier devices in this family (LAN9500/9512/9514) do not
> support this fea
CC linux-power
On Tue, Dec 11, 2012 at 11:19 PM, Oliver Neukum wrote:
> On Tuesday 11 December 2012 20:53:19 Ming Lei wrote:
>> In fact, I have test data which can show a much power save
>> on OMAP3 based beagle board plus asix usbnet device with
>> the periodic work. IMO, the power save after in
On Mon, 10 Dec 2012, Golmer Palmer wrote:
> Alan Stern writes:
>
> >
> > On Mon, 10 Dec 2012, Golmer Palmer wrote:
> >
> > > Now, another comment related to the "storage_common.c" file:
> > >
> > > Why the limit of "if (num_sectors >= 256*60*75*4)" in function
> "fsg_lun_open()".
> >
> > T
On Mon, 10 Dec 2012, Timur wrote:
> N7 is not using a vanilla kernel. It is one thing to apply modifications
> to the given code base. It would be far more difficult (I think) to
> replace the kernel as a whole. Maybe I should back port just as little
> code as possible? Or maybe I should try t
This patch enables USB dynamic autosuspend for LAN9500A. This
saves very little power in itself, but it allows power saving
in upstream hubs/hosts.
The earlier devices in this family (LAN9500/9512/9514) do not
support this feature.
Signed-off-by: Steve Glendinning
---
drivers/net/usb/smsc95xx.
On Tuesday 11 December 2012 20:53:19 Ming Lei wrote:
> In fact, I have test data which can show a much power save
> on OMAP3 based beagle board plus asix usbnet device with
> the periodic work. IMO, the power save after introducing periodic
> timer depends on the arch or platform, there should be m
On 11 December 2012 12:53, Ming Lei wrote:
> On Tue, Dec 11, 2012 at 6:27 PM, Oliver Neukum wrote:
>> So they can autosuspend if the interface is up and no cable is plugged
>> in?
>
> From the open datasheet, that is the suspend 1 mode, which is supported
> by all LAN95xx devices. Steve, correct
On Tue, Dec 11, 2012 at 6:27 PM, Oliver Neukum wrote:
> On Tuesday 11 December 2012 10:24:57 Ming Lei wrote:
>> On Mon, Dec 10, 2012 at 10:18 PM, Steve Glendinning
>> wrote:
>
>> > Thanks, so something like this should do the job?
>>
>> This will do, but not simple as clearing .manage_power func
> > > > >
> > > > > I am working on a new UDC for a new USB chip. The kernel version
> > > > > is 3.4.4. When I insmod the new UDC, it is ok. When I insmod the
> > > > > file
> > >
> > > out of curiosity, do you plan to send kagen2_udc.ko to mainline ?
> > >
> > Yes, it will be sent to mainline onc
From: fangxiaozhi
To optimize the match rules for the Huawei USB storage devices. Avoid to load
USB storage driver for modem interface with Huawei devices.
Signed-off-by: fangxiaozhi
-
diff -uprN linux-3.7_bak/dri
On Tuesday 11 December 2012 10:24:57 Ming Lei wrote:
> On Mon, Dec 10, 2012 at 10:18 PM, Steve Glendinning wrote:
> > Thanks, so something like this should do the job?
>
> This will do, but not simple as clearing .manage_power function
> pointer in bind(), and still disable runtime suspend for l
On Tue, Dec 11, 2012 at 12:01:57PM +0200, Roger Quadros wrote:
> On 12/11/2012 11:12 AM, Jassi Brar wrote:
> > On Mon, Dec 10, 2012 at 3:18 PM, Roger Quadros wrote:
> >> On 12/06/2012 04:34 PM, Jassi Brar wrote:
>
> Yes, this is where we can think of a generic PHY driver to make sure thy
On 12/11/2012 11:12 AM, Jassi Brar wrote:
> On Mon, Dec 10, 2012 at 3:18 PM, Roger Quadros wrote:
>> On 12/06/2012 04:34 PM, Jassi Brar wrote:
Yes, this is where we can think of a generic PHY driver to make sure thy
PHY has necessary resources enabled. In the Panda case it would be
On Mon, Dec 10, 2012 at 3:18 PM, Roger Quadros wrote:
> On 12/06/2012 04:34 PM, Jassi Brar wrote:
>>>
>>> Yes, this is where we can think of a generic PHY driver to make sure thy
>>> PHY has necessary resources enabled. In the Panda case it would be the
>>> PHY clock and RESET gpio.
>>>
>> I wonde
Hi,
On Tue, Dec 11, 2012 at 10:07:51AM +0800, victor wrote:
> > > do I insmod the file storage gadget separately? The /dev/mmcblk0 refers
> to
> > SD card, right? I insmod the sd card driver already.
> > >
> > > # lsmod
> > > kagen2_udc 7262 0 - Live 0xbf02f000
> > > ka2000_sdio 6643 0 - Live 0xbf
On Tue, Dec 11, 2012 at 10:08:52AM +0800, victor wrote:
> > > >
> > > > I am working on a new UDC for a new USB chip. The kernel version is
> > > > 3.4.4. When I insmod the new UDC, it is ok. When I insmod the file
> >
> > out of curiosity, do you plan to send kagen2_udc.ko to mainline ?
> >
> Ye
Hi Alan&Greg:
Since 3.1, Alan enabled usb device wakeup default, there are
a lot of problem that immediately resume when enter into s2ram/s2disk.
I have traced some these bugs. Most of these bugs are related usb1.1
device which attached to OHCI/UHCI. If disable the hc wakeup or no device
67 matches
Mail list logo
