On Thu, 2015-04-02 at 14:26 +0200, Jiri Kosina wrote:
> On Wed, 1 Apr 2015, Oliver Neukum wrote:
>
> > > I am postponing all these before it is clarified that this is indeed a
> > > case reporter is able to reproduce on different system as well to rule
> > > out
> > > the possibility of hub bei
On Tue, Apr 07, 2015 at 10:27:15PM +0200, Matthias Nagel wrote:
> Obeying to a wish made by Greg Kroah-Hartman I hereby send my bug
> report [1] to this list. I do not include the attachments as the can
> be found at [1]. The description:
Please send the attachments, no one wants to dig for web li
Since the DT should describe the hardware (not the driver limitation),
This patch revises the binding document about the dma-names to change
simple numbering as "ch%d" instead of "tx" and "rx".
Also this patch fixes the actual code of renesas_usbhs driver to handle
the new dma-names.
Signed-off-b
>>
>> USB 2.01+ full-speed devices can have extended descriptor as well
>> and can support LPM.
>
> Yes, they in theory can, but what happens if they are actually
> asked to do so? On how many devices have you tested this patch?
>
I have tested this on Qualcomm USB controller, LPM works. LPM works
> On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
>> From: Rupesh Tatiya
>>
>> USB 2.01+ full-speed devices can have extended descriptor as well
>> and can support LPM.
>>
>> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
>
> We can't take patches with this in it, as
Luns in mass storage function are identified using their id.
While creating lun's directory user cannot choose any arbitrary
name other than arabic numeral from 1 to FSG_MAX_LUNS.
Signed-off-by: Krzysztof Opasiak
---
.../ABI/testing/configfs-usb-gadget-mass-storage |7 ++-
1 file chang
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_mass_storage.c | 35 +++---
1 file changed, 31 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
b/drivers/usb/gadget/function/f_mass_storage.c
index 095b618..9d9fafb 1
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_mass_storage.c |5 +
drivers/usb/gadget/function/f_mass_storage.h |1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
b/drivers/usb/gadget/function/f_mass_storage.c
index
Sometimes it might be desirable to prohibit removing a directory
in configfs. One example is USB gadget (mass_storage function):
when gadget is already bound, if lun directory is removed,
the gadget must be thrown away, too. A better solution would be
to fail with e.g. -EBUSY.
Currently configfs h
Signed-off-by: Krzysztof Opasiak
---
fs/configfs/dir.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/configfs/dir.c b/fs/configfs/dir.c
index cf0db00..dee1cb5 100644
--- a/fs/configfs/dir.c
+++ b/fs/configfs/dir.c
@@ -325,7 +325,7 @@ static void configfs_dir_set_ready(
Dear list,
This series fix configfs interface for mass storage function.
According to mass storage specification[1]:
"Logical Unit Numbers on the device shall be numbered contiguously
starting from LUN 0 to a maximum LUN of 15 (Fh)."
Currently configfs interface allows to create LUNs with
arbit
On Wed, Apr 08, 2015 at 11:27:40AM -, rtat...@codeaurora.org wrote:
> > On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
> >> From: Rupesh Tatiya
> >>
> >> USB 2.01+ full-speed devices can have extended descriptor as well
> >> and can support LPM.
> >>
> >> Change-Id: Ic
Sometimes it might be desirable to prohibit removing a directory
in configfs. One example is USB gadget (mass_storage function):
when gadget is already bound, if lun directory is removed,
the gadget must be thrown away, too. A better solution would be
to fail with e.g. -EBUSY.
Currently configfs h
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_mass_storage.c |5 +
drivers/usb/gadget/function/f_mass_storage.h |1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
b/drivers/usb/gadget/function/f_mass_storage.c
index
Luns in mass storage function are identified using their id.
While creating lun's directory user cannot choose any arbitrary
name other than arabic numeral from 1 to FSG_MAX_LUNS.
Signed-off-by: Krzysztof Opasiak
---
.../ABI/testing/configfs-usb-gadget-mass-storage |7 ++-
1 file chang
Dear list,
This series fix configfs interface for mass storage function.
According to mass storage specification[1]:
"Logical Unit Numbers on the device shall be numbered contiguously
starting from LUN 0 to a maximum LUN of 15 (Fh)."
Currently configfs interface allows to create LUNs with
arbit
Signed-off-by: Krzysztof Opasiak
---
drivers/usb/gadget/function/f_mass_storage.c | 35 +++---
1 file changed, 31 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/function/f_mass_storage.c
b/drivers/usb/gadget/function/f_mass_storage.c
index 095b618..9d9fafb 1
Hi!
Excuse me, did not understand your message.
You offer to throw out all of the devices that do not work? But this
device is works. Very rear occurs described situation.
I write here because hope that can make do some thing with kernel. For
example software reset hub etc.
--
Best Regards,
Mike
On Wed, Apr 08, 2015 at 11:42:24AM +0100, Yoshihiro Shimoda wrote:
> Since the DT should describe the hardware (not the driver limitation),
> This patch revises the binding document about the dma-names to change
> simple numbering as "ch%d" instead of "tx" and "rx".
The naming given in this patch
>> On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
>>> From: Rupesh Tatiya
>>>
>>> USB 2.01+ full-speed devices can have extended descriptor as well
>>> and can support LPM.
>>>
>>> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
>>
>> We can't take patches with this i
On Wed, 8 Apr 2015, Krzysztof Opasiak wrote:
> Signed-off-by: Krzysztof Opasiak
> ---
> drivers/usb/gadget/function/f_mass_storage.c |5 +
> drivers/usb/gadget/function/f_mass_storage.h |1 +
> 2 files changed, 6 insertions(+)
>
> diff --git a/drivers/usb/gadget/function/f_mass_stor
On Wed, 8 Apr 2015, Михаил Гаврилов wrote:
> Hi!
> Excuse me, did not understand your message.
> You offer to throw out all of the devices that do not work?
No, you don't have to throw out all the devices. Just try a different
hub.
> But this
> device is works. Very rear occurs described situ
On Wed, 8 Apr 2015, Steve Bangert wrote:
> What i did was not correct, usb-storage.quirks=174c:55aa:u was added to
> /etc/default/grub file after GRUB_CMDLINE_LINUX="rhgb quiet", using
> the grub-configurator tool
> followed by a reboot and i now have a working usb storage device
> using xhci. Her
Hi,
On 04/08/2015 04:15 PM, Alan Stern wrote:> On Wed, 8 Apr 2015, Krzysztof
Opasiak wrote:
>
>> Signed-off-by: Krzysztof Opasiak
>> ---
>> drivers/usb/gadget/function/f_mass_storage.c |5 +
>> drivers/usb/gadget/function/f_mass_storage.h |1 +
>> 2 files changed, 6 insertions(
Am Mittwoch, 8. April 2015, 10:40:39 schrieb Greg KH:
>
> Please send the attachments, no one wants to dig for web links :(
Here they are.
>
> This really sounds like some broken hardware as there's nothing that the
> kernel can do to disconnect/reconnect a device like this. Given that
> your
Add missing directions, residue_granularity,
srd_addr_widths and dst_addr_widths bitfields.
Without those we will see a kernel WARN()
when loading musb on am335x devices.
Signed-off-by: Felipe Balbi
---
retested with AM335x BeagleBone Black
drivers/dma/cppi41.c | 9 +
1 file changed,
Everyone, thank you for your attention and suggestions.
Johan, perfect, thank you, that did indeed help and has fixed the issue I was
seeing.
The change replaced dev_err() with dev_dbg() -- thus not logging (by default)
what
was a very noisy flood of messages. Does that simply change timing eno
Hi,
When connecting cx231xx video grab devices (which are USB 2.0
themselves) on ASMedia ASM1042A USB 3.0 Host Controllers the video
capture process hangs after a few minutes. Besides hanging my log is
flowed with the following warning:
xhci_hcd :05:00.0: WARN Successful completion on short
On Wed, Apr 8, 2015 at 2:45 PM, Rodrigo Severo
wrote:
>
> Please let me know if there is any extra info that might help further
> diagnose this issue.
Please disregard the lsusb log on my previous email as I just saw that
it lacks lots of info from the cx231xx video grab device. I believe
this is
Hi Robert,
On 04/02/2015 10:13 PM, Robert Baldyga wrote:
> This patch adds VBUS pin detection support to extcon-usb-gpio driver.
> It allows to use this driver with boards which have both VBUS and ID
> pins, or only one of them.
>
> Following table of states presents relationship between this sig
Hi Mark,
>
> On Wed, Apr 08, 2015 at 11:42:24AM +0100, Yoshihiro Shimoda wrote:
> > Since the DT should describe the hardware (not the driver limitation),
> > This patch revises the binding document about the dma-names to change
> > simple numbering as "ch%d" instead of "tx" and "rx".
>
> The na
Windows appears to pay more attention to the ACPI values than any hub
configuration, so prefer the firmware's opinion on whether a port is
fixed or removable before falling back to the hub values.
Signed-off-by: Matthew Garrett
---
drivers/usb/core/hub.c | 32 +---
1
The Microsoft document "Using ACPI to Configure USB Ports on a Computer"
makes it clear that the removable flag will be cleared on ports that are
marked as unused by the firmware. Handle this case to match.
Signed-off-by: Matthew Garrett
---
drivers/usb/core/hub.c | 3 +++
1 file changed, 3 inse
33 matches
Mail list logo
