On 12/11/2013 08:41 PM, Alan Stern wrote:
On Wed, 11 Dec 2013, Eugene Shatokhin wrote:
Hi,
On ROSA Linux with kernel 3.10.21 with DMA debug options enabled, the
kernel sometimes issues a warning about DMA pool corruption (see the log
below).
That happens sometimes, when the system boots or re
On 13 December 2013 06:18, David Cohen wrote:
> From: Santosh Shilimkar
>
> Drivers using SET_*_PM_OPS() no longer need to #ifdef for CONFIG_PM_*
> So, let's remove the unnecessary #ifdef's.
>
> Signed-off-by: Santosh Shilimkar
> Signed-off-by: David Cohen
> ---
> drivers/usb/host/xhci-plat.c
From: Freddy Xin
The AX88179_178A has a hardware feature that it can insert a
2-bytes pseudo header in front of each received frame by setting
the AX_RX_CTL_IPE bit. This feature is used to let the IP header
be aligned on a doubleword-aligned address, so the rx_submit() of
usbnet.c needn't reserv
On Thursday 12 December 2013 11:48 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Dec 12, 2013 at 08:26:02AM -0500, Matt Porter wrote:
>> This adds a pair of APIs that allows the generic PHY subsystem to
>> provide information on the PHY bus width. The PHY provider driver may
>> use phy_set_bus_width()
Hello Lee Jones,
The patch 5f6091a023ca: "usb: musb: ux500: harden checks for platform
data" from May 15, 2013, leads to the following
static checker warning: "drivers/usb/musb/ux500_dma.c:335
ux500_dma_controller_start()
error: potential NULL dereference 'param_array'."
drivers/usb/musb
On 12/12/2013 08:14 PM, Paul Zimmerman wrote:
>> From: linux-usb-ow...@vger.kernel.org
>> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Robert Baldyga
>> Sent: Thursday, December 12, 2013 12:51 AM
>>
>> This patch adds "maxpacket_limit" to struct usb_ep. This field contains
>> maximum valu
> From: fre...@asix.com.tw
...
> - skb = __netdev_alloc_skb_ip_align(dev->net, size, flags);
> + if (dev->driver_info->flags & FLAG_HW_IPALIGN)
> + skb = __netdev_alloc_skb(dev->net, size, flags);
> + else
> + skb = __netdev_alloc_skb_ip_align(dev->net, size, fla
static checker warning: "drivers/usb/musb/ux500_dma.c:335
ux500_dma_controller_start()
error: potential NULL dereference 'param_array'."
Reported-by: Dan Carpenter
Signed-off-by: Lee Jones
---
drivers/usb/musb/ux500_dma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff -
On Thursday 12 December 2013 06:56 PM, Matt Porter wrote:
> If a generic phy is present, call phy_init()/phy_exit(). This supports
> generic phys that must be soft reset before power on.
>
> Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
> ---
> drivers/usb/gadget/s3c-hsotg.c | 5 +
On Thursday 12 December 2013 06:56 PM, Matt Porter wrote:
> Adds support for querying the phy bus width from the generic phy
> subsystem. Configure UTMI bus width in GUSBCFG based on this value.
>
> Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
> ---
> drivers/usb/gadget/s3c-hsotg
Hello Andrzej Pietrasiewicz,
The patch 83167f12da05: "usb: gadget: nokia: convert to new interface
of f_phonet" from May 23, 2013, leads to the following Smatch
warnings:
drivers/usb/gadget/nokia.c:209 nokia_bind_config() error: potential NULL
dereference 'f_obex2'.
drivers/usb/gadget/nokia.c:21
This patch adds "maxpacket_limit" to struct usb_ep. This field contains
maximum value of maxpacket supported by driver, and is set in driver probe.
This value should be used by autoconfig() function, because value of field
"maxpacket" is set to value from endpoint descriptor when endpoint becomes
e
hi
2013/12/2 Alan Stern :
> On Sun, 1 Dec 2013, vichy wrote:
>
>> hi Alan:
>>
>> 2013/12/1 Alan Stern :
>> > On Fri, 29 Nov 2013, vichy wrote:
>> >
>> >> hi all:
>> >> My connection like below
>> >> ehci --> high speed hub -> full speed device
>> >>
>> >> I have some questions about period schedul
On Thu, Dec 12, 2013 at 11:29 PM, Andreas Naumann wrote:
> Hi Grazvydas,
>
>> Von: Grazvydas Ignotas [mailto:nota...@gmail.com]
>> Gesendet: Donnerstag, 12. Dezember 2013 01:21
>> An: linux-usb@vger.kernel.org
>> Cc: Felipe Balbi; linux-o...@vger.kernel.org; Naumann Andreas; Grazvydas
>> Ignotas;
Hello! I am new to this group and hope you can help me out.
I am on an embedded board with an ARM cortex a5 and using gadgetfs.
An Application that is derived from the usb.c example is running on it while
the board is connected to a PC with the USB 2.0 Command Verifier.
I am quite new to developm
Hello Dan Carpenter,
Thank you for your comments.
W dniu 13.12.2013 12:22, Dan Carpenter pisze:
Hello Andrzej Pietrasiewicz,
The patch 83167f12da05: "usb: gadget: nokia: convert to new interface
of f_phonet" from May 23, 2013, leads to the following Smatch
warnings:
drivers/usb/gadget/nokia.c
Hi Macro,
We have observed same issue and reason for this issue is reset_config which
triggers complete USB disconnect from F_FS.
For SET_CONFIG(Config#0) there is no need to do USB Disconnect. This seems to
be bottleneck issue for USB compliance.
I believe this issue should be addressed by Gad
On 2013-12-10 16:03, Oliver Neukum wrote:
>> Thanks, but some of the messages look quite hardcoded.
>> Is there a patch to get rid of them?
>
> More patches concerning dynamic debugging are in the queue for 3.14
> It looks like on your system it is by default switched on. You
> can switch it off a
Hi,
Recently, we encountered one issue in Kernel 3.10(On Android 4.4) where USB
enumeration is falling after many connect/disconnect.
The reason for this issue is, we started using usb_gstrings_attach for string
update in configuration and cdev->next_string_id is never set to 0 in
disconnect c
In the nokia gadget some USB functions (obex 1 and 2, phonet) are optional.
If at the start of nokia_bind_config e.g. fi_phonet is an error pointer,
which can happen because we don't fail the bind process if
usb_get_function_instance() fails for fi_phonet, then f_phonet is NULL, and
phonet_stat =
From: Kamil Debski
Adding devm_of_phy_get will allow to get phys by supplying the
device_node instead of by name.
Signed-off-by: Kamil Debski
---
drivers/phy/phy-core.c | 31 +++
include/linux/phy/phy.h |2 ++
2 files changed, 33 insertions(+)
diff --git a/d
From: Kamil Debski
Previously the of_phy_get function took a struct device * and
was declared static. It was impossible to call it from
another driver and thus it was impossible to get phy defined
for a given node. The old function was renamed to _of_phy_get
and was left for internal use. of_phy_
Adding devm_of_phy_get will allow to get phys by supplying the
device_node instead of by name.
Signed-off-by: Kamil Debski
---
It seems that my git send-email is playing up and sent the previous emails
without from. This is a resend. Sorry for any confusion.
---
drivers/phy/phy-core.c | 31 ++
Previously the of_phy_get function took a struct device * and
was declared static. It was impossible to call it from
another driver and thus it was impossible to get phy defined
for a given node. The old function was renamed to _of_phy_get
and was left for internal use. of_phy_get function was adde
Hi,
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Monday, December 09, 2013 8:23 AM
>
> On Friday 06 December 2013 04:22 PM, Kamil Debski wrote:
> > Hi,
> >
> >> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> >> Sent: Friday, December 06, 2013 6:31 AM
> >>
> >> Hi,
> >>
>
Hi,
Am 02.10.2013 um 09:00 schrieb Dr. H. Nikolaus Schaller:
> Hi Jan,
>
> we are using a GTM601 modem (Firmware 1.7) for a while and have spotted an
> issue that under some conditions the modem sends a packed wIndex over USB
> that is rejected by the hso driver making troubles afterwards. Not r
Hi,
On Friday 13 December 2013 07:32 PM, Kamil Debski wrote:
> Previously the of_phy_get function took a struct device * and
> was declared static. It was impossible to call it from
> another driver and thus it was impossible to get phy defined
> for a given node. The old function was renamed to _
Hello together,
is there anything new for the PL-2303 HX?
It would be fine if it could work like in the past.
Of course for Linux there are good alternatives.
Here is a new one with the CP2102 suffering easy supply voltage:
http://www.ebay.de/itm/110954294607
Best regards
Karsten
Am 24.06.201
Hi Kishon,
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Friday, December 13, 2013 3:45 PM
>
> Hi,
>
> On Friday 13 December 2013 07:32 PM, Kamil Debski wrote:
> > Previously the of_phy_get function took a struct device * and was
> > declared static. It was impossible to call it
On Fri, Dec 13, 2013 at 09:19:34AM +0100, Ulf Hansson wrote:
> On 13 December 2013 06:18, David Cohen wrote:
> > From: Santosh Shilimkar
> >
> > Drivers using SET_*_PM_OPS() no longer need to #ifdef for CONFIG_PM_*
> > So, let's remove the unnecessary #ifdef's.
> >
> > Signed-off-by: Santosh Shil
Hello
> -Original Message-
> From: Shilimkar, Santosh
> Sent: Thursday, December 12, 2013 7:29 PM
> To: Balbi, Felipe
> Cc: Linux USB Mailing List; kgene@samsung.com; Linux ARM Kernel
> Mailing List; linux-samsung-...@vger.kernel.org; Linux OMAP Mailing List;
> Kwok, WingMan
> Subject:
On 13.12.2013 13:34, Grazvydas Ignotas wrote:
On Thu, Dec 12, 2013 at 11:29 PM, Andreas Naumann wrote:
Hi Grazvydas,
Von: Grazvydas Ignotas [mailto:nota...@gmail.com]
Gesendet: Donnerstag, 12. Dezember 2013 01:21
An: linux-usb@vger.kernel.org
Cc: Felipe Balbi; linux-o...@vger.kernel.org; Naum
On Fri, Dec 13, 2013 at 02:31:47PM +, Chris Clayton wrote:
> Hi,
Hi Chris,
Thanks for the bug report!
> Firstly, I'm not subscribed, so please cc me on any replies.
>
> I see the problem I describe below on 3.12.[0..5] and on the current 3.13
> development kernel, including a kernel pulled
On Thu, 12 Dec 2013, Felipe Balbi wrote:
> > Felipe:
> >
> > Is the usb_enumerate_device_otg() routine really correct? It looks
> > like it will try to enable HNP whenever CONFIG_USB_OTG is set, even if
> > the root hub isn't OTG-capable.
> >
> > The routine does this:
> >
> >
Adds support for querying the phy bus width from the generic phy
subsystem. Configure UTMI bus width in GUSBCFG based on this value.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
drivers/usb/gadget/s3c-hsotg.c | 14 +-
drivers/usb/gadget/s3c-hsotg.h | 1 +
2 files
Add a driver for the internal Broadcom Kona USB 2.0 PHY found
on the BCM281xx family of SoCs.
Signed-off-by: Matt Porter
---
drivers/phy/Kconfig | 6 ++
drivers/phy/Makefile| 1 +
drivers/phy/phy-bcm-kona-usb2.c | 158
3 files
On Fri, 13 Dec 2013, vichy wrote:
> hi
>
> 2013/12/2 Alan Stern :
> > On Sun, 1 Dec 2013, vichy wrote:
> >
> >> hi Alan:
> >>
> >> 2013/12/1 Alan Stern :
> >> > On Fri, 29 Nov 2013, vichy wrote:
> >> >
> >> >> hi all:
> >> >> My connection like below
> >> >> ehci --> high speed hub -> full speed
Adds USB OTG/PHY and clock support to BCM281xx and enables
UDC support on the bcm11351-brt and bcm28155-ap boards.
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
Reviewed-by: Tim Kryger
---
arch/arm/boot/dts/bcm11351-brt.dts | 6 ++
arch/arm/boot/dts/bcm11351.dtsi| 18 ++
If a generic phy is present, call phy_init()/phy_exit(). This supports
generic phys that must be soft reset before power on.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
drivers/usb/gadget/s3c-hsotg.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/usb/gadget
Add a binding that describes the Broadcom Kona USB2 PHY found
on the BCM281xx family of SoCs.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/bcm-phy.txt | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 Documentatio
Changes since v5:
- tweak s3c-hsotg Kconfig help message to be more generic
Changes since v4:
- phy_set/get_bus_width now use an int for bus_width
Changes since v3:
- Rebased on 3.13-rc3
- Move struct phy bus_width attribute back into struct phy_attrs
- Fix
Remove unused Samsung-specific machine include and Kconfig
dependency on S3C.
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
Reviewed-by: Tim Kryger
---
drivers/usb/gadget/Kconfig | 7 +++
drivers/usb/gadget/s3c-hsotg.c | 2 --
2 files changed, 3 insertions(+), 6 deletions(-)
di
This adds a pair of APIs that allows the generic PHY subsystem to
provide information on the PHY bus width. The PHY provider driver may
use phy_set_bus_width() to set the bus width that the PHY supports.
The controller driver may then use phy_get_bus_width() to fetch the
PHY bus width in order to p
Enable support for the dwc2 binding.
Signed-off-by: Matt Porter
---
drivers/usb/gadget/s3c-hsotg.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/s3c-hsotg.c b/drivers/usb/gadget/s3c-hsotg.c
index 8ceb5ef..7c5d8bd 100644
--- a/drivers/usb/gadget/s3c-hsotg.c
+++ b/drivers/
dwc2/s3c-hsotg require a single clock to be specified and optionally
a generic phy. On the s3c-hsotg driver old style USB phy support is
present as a fallback so the generic phy properties are optional.
Signed-off-by: Matt Porter
Acked-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bin
On Tue, May 28, 2013 at 07:40:57PM +0200, Holger Hans Peter Freyther wrote:
Good Evening,
> Is there a timeline when you think this could be fixed?
I tried with 3.10.x and 3.12.5 and the symptoms remain the same. The first
time it is working, the second time the scanning does not start. The sc
On Thu, Dec 12, 2013 at 11:05:04AM -0500, Alan Stern wrote:
> On Wed, 11 Dec 2013, Julius Werner wrote:
>
> > >> ...although, the spec says that it does not wait for the port resets
> > >> to complete. As far as I can see re-issuing a warm reset and waiting
> > >> is the only way to guarantee the
Hi Sarah,
On Fri, Dec 13, 2013 at 09:48:15AM -0800, Sarah Sharp wrote:
> On Thu, Dec 12, 2013 at 11:05:04AM -0500, Alan Stern wrote:
> > On Wed, 11 Dec 2013, Julius Werner wrote:
> >
> > > >> ...although, the spec says that it does not wait for the port resets
> > > >> to complete. As far as I c
On Fri, Dec 13, 2013 at 9:48 AM, Sarah Sharp
wrote:
> On Thu, Dec 12, 2013 at 11:05:04AM -0500, Alan Stern wrote:
>> On Wed, 11 Dec 2013, Julius Werner wrote:
>>
>> > >> ...although, the spec says that it does not wait for the port resets
>> > >> to complete. As far as I can see re-issuing a warm
On Thu, Dec 12, 2013 at 05:04:31PM -0500, Alan Stern wrote:
> On Wed, 11 Dec 2013, Sarah Sharp wrote:
>
> > Hi Hans,
> >
> > I've been testing the UAS code you sent a pull request for against
> > 3.13-rc1, and I've run into a rather nasty issue with USB disconnect.
> >
> > I ran some tests with
On Fri, 13 Dec 2013, Dan Williams wrote:
> > I'm actually leaning towards enabling the check for warm reset broadly.
> > It seems like it wouldn't hurt to issue a warm reset on the USB 3.0
> > ports if they're in compliance, poll, or rx.detect. So, let's enable
> > this broadly in xhci_resume, ma
On Fri, 13 Dec 2013, Sarah Sharp wrote:
> > Given the way things work now, I suspect these warnings are truly
> > harmless. We could simply get rid of the WARN in sysfs_remove_group.
> >
> > The alternative is to call device_del for SCSI targets earlier on, such
> > as when their hosts are unr
On Fri, Dec 13, 2013 at 10:15 AM, Alan Stern wrote:
> On Fri, 13 Dec 2013, Dan Williams wrote:
>
>> > I'm actually leaning towards enabling the check for warm reset broadly.
>> > It seems like it wouldn't hurt to issue a warm reset on the USB 3.0
>> > ports if they're in compliance, poll, or rx.de
On Fri, Dec 13, 2013 at 10:00:28AM -0800, David Cohen wrote:
> Hi Sarah,
>
> On Fri, Dec 13, 2013 at 09:48:15AM -0800, Sarah Sharp wrote:
> > On Thu, Dec 12, 2013 at 11:05:04AM -0500, Alan Stern wrote:
> > > On Wed, 11 Dec 2013, Julius Werner wrote:
> > >
> > > > >> ...although, the spec says tha
Hello, guys.
(cc'ing Greg)
On Fri, Dec 13, 2013 at 01:19:36PM -0500, Alan Stern wrote:
> On Fri, 13 Dec 2013, Sarah Sharp wrote:
>
> > > Given the way things work now, I suspect these warnings are truly
> > > harmless. We could simply get rid of the WARN in sysfs_remove_group.
> > >
> > > The
On Fri, Dec 13, 2013 at 01:19:36PM -0500, Alan Stern wrote:
> On Fri, 13 Dec 2013, Sarah Sharp wrote:
>
> > > Given the way things work now, I suspect these warnings are truly
> > > harmless. We could simply get rid of the WARN in sysfs_remove_group.
> > >
> > > The alternative is to call devic
On Fri, 2013-12-13 at 13:33 -0500, Tejun Heo wrote:
> Hello, guys.
>
> (cc'ing Greg)
>
> On Fri, Dec 13, 2013 at 01:19:36PM -0500, Alan Stern wrote:
> > On Fri, 13 Dec 2013, Sarah Sharp wrote:
> >
> > > > Given the way things work now, I suspect these warnings are truly
> > > > harmless. We co
Hi David,
All right, I'm finally starting to catch up on my patch queue. :)
Sorry for the delay.
In general this looks like a good patch, thanks for submitting it.
However, there's a couple things I need you to fix.
On Mon, Nov 04, 2013 at 11:36:00AM -, David Laight wrote:
> In many cases th
On Fri, Dec 13, 2013 at 11:47:56AM -0800, Sarah Sharp wrote:
> Hi David,
>
> All right, I'm finally starting to catch up on my patch queue. :)
> Sorry for the delay.
>
> In general this looks like a good patch, thanks for submitting it.
> However, there's a couple things I need you to fix.
Ah, I
Hi,
On Fri, Dec 13, 2013 at 08:48:30AM +0100, Andreas Larsson wrote:
> >On Wed, Dec 04, 2013 at 09:13:58AM +0100, Andreas Larsson wrote:
> >>+static void gr_finish_request(struct gr_ep *ep, struct gr_request *req,
> >>+ int status)
> >>+{
> >>+ struct gr_udc *dev;
> >>+
>
On Mon, Nov 04, 2013 at 11:32:41AM -, David Laight wrote:
> Replace the array of pointers to transfer descriptors with
> the transfer descriptors themselves.
>
> This saves a kzalloc() call on every transfer and some memory
> indirections.
>
> The only possible downside is for isochronous tra
On Fri, Dec 13, 2013 at 10:04:38AM -0600, Kwok, WingMan wrote:
> Hello
>
> > -Original Message-
> > From: Shilimkar, Santosh
> > Sent: Thursday, December 12, 2013 7:29 PM
> > To: Balbi, Felipe
> > Cc: Linux USB Mailing List; kgene@samsung.com; Linux ARM Kernel
> > Mailing List; linux-s
On Fri, Dec 13, 2013 at 02:01:32PM +0900, Anton Tikhomirov wrote:
> Hi Felipe,
>
> > -static int dwc3_exynos_suspend(struct device *dev)
> > +static int __dwc3_exynos_suspend(struct dwc3_exynos *exynos)
> > {
> > - struct dwc3_exynos *exynos = dev_get_drvdata(dev);
> > -
> > clk_disable(exy
hi,
On Fri, Dec 13, 2013 at 01:36:03PM +, roshan.jhal...@broadcom.com wrote:
> Hi Macro,
>
> We have observed same issue and reason for this issue is reset_config
> which triggers complete USB disconnect from F_FS. For
> SET_CONFIG(Config#0) there is no need to do USB Disconnect. This
> see
On Fri, 2013-12-13 at 11:18 -0800, James Bottomley wrote:
> On Fri, 2013-12-13 at 13:33 -0500, Tejun Heo wrote:
> > Hello, guys.
> >
> > (cc'ing Greg)
> >
> > On Fri, Dec 13, 2013 at 01:19:36PM -0500, Alan Stern wrote:
> > > On Fri, 13 Dec 2013, Sarah Sharp wrote:
> > >
> > > > > Given the way t
On Fri, 13 Dec 2013, James Bottomley wrote:
> > > I wasn't clear on the reason for that problem. Does it also arise from
> > > late device_del for scsi_target? I could try to change the way that
> > > works, if anybody (Hans?) would like to test it.
> >
> > While the recent sysfs changes made
On Wed, Nov 13, 2013 at 10:24:00AM -, David Laight wrote:
> > Greg KH wrote:
> > On Tue, Nov 12, 2013 at 01:58:05PM -, David Laight wrote:
> > >
> > > There needs to be a wmb() barrier between the write to the cycle bit
> > > in the first TRB and the write to the doorbell register.
> > >
>
On Mon, Nov 11, 2013 at 04:15:26PM -, David Laight wrote:
>
> This makes it clear that the ring->cycle_state value is used when
> writing to the actual ring itself.
>
> Always use ^= TRB_CYCLE to invert the bit.
>
> Signed-off-by: David Laight
> ---
> Changes for v2:
>
> 1 Adjusted so that
On Fri, Dec 13, 2013 at 02:31:42PM +0800, Peter Chen wrote:
> On Fri, Dec 13, 2013 at 12:32 PM, Felipe Balbi wrote:
> > On Fri, Dec 13, 2013 at 09:23:38AM +0800, Peter Chen wrote:
> >> Implementation of notify_suspend and notify_resume will be different
> >> according to mxs_phy_data->flags.
> >>
> -Original Message-
> From: Balbi, Felipe
> Sent: Friday, December 13, 2013 2:55 PM
> To: Kwok, WingMan
> Cc: Shilimkar, Santosh; Balbi, Felipe; Linux USB Mailing List;
> kgene@samsung.com; Linux ARM Kernel Mailing List; linux-samsung-
> s...@vger.kernel.org; Linux OMAP Mailing List
>
On Fri, Dec 13, 2013 at 01:56:18PM -0600, Felipe Balbi wrote:
> On Fri, Dec 13, 2013 at 02:01:32PM +0900, Anton Tikhomirov wrote:
> > Hi Felipe,
> >
> > > -static int dwc3_exynos_suspend(struct device *dev)
> > > +static int __dwc3_exynos_suspend(struct dwc3_exynos *exynos)
> > > {
> > > - struct
Hi James,
On 12/13/2013 09:03 PM, James Bottomley wrote:
On Fri, 2013-12-13 at 11:18 -0800, James Bottomley wrote:
On Fri, 2013-12-13 at 13:33 -0500, Tejun Heo wrote:
Hello, guys.
(cc'ing Greg)
On Fri, Dec 13, 2013 at 01:19:36PM -0500, Alan Stern wrote:
On Fri, 13 Dec 2013, Sarah Sharp wrot
On Fri, Dec 13, 2013 at 02:18:42PM -0600, Kwok, WingMan wrote:
>
> > -Original Message-
> > From: Balbi, Felipe
> > Sent: Friday, December 13, 2013 2:55 PM
> > To: Kwok, WingMan
> > Cc: Shilimkar, Santosh; Balbi, Felipe; Linux USB Mailing List;
> > kgene@samsung.com; Linux ARM Kernel M
On Fri, 13 Dec 2013, James Bottomley wrote:
> Actually, I think I have this figured out. There's a thinko in one of
> the scsi_target_reap() cases. The original (and still existing) problem
> with targets is that nothing creates them and nothing destroys them, so,
> while we could rely on the re
On Fri, Dec 13, 2013 at 12:03:19PM -0800, James Bottomley wrote:
> Actually, I think I have this figured out. There's a thinko in one of
> the scsi_target_reap() cases. The original (and still existing) problem
> with targets is that nothing creates them and nothing destroys them, so,
> while we
On Fri, 2013-12-13 at 16:06 -0500, Alan Stern wrote:
> On Fri, 13 Dec 2013, James Bottomley wrote:
>
> > Actually, I think I have this figured out. There's a thinko in one of
> > the scsi_target_reap() cases. The original (and still existing) problem
> > with targets is that nothing creates them
Hi,
On 12/13/2013 09:03 PM, James Bottomley wrote:
Actually, I think I have this figured out. There's a thinko in one of
the scsi_target_reap() cases. The original (and still existing) problem
with targets is that nothing creates them and nothing destroys them, so,
while we could rely on th
> -Original Message-
> From: Balbi, Felipe
> Sent: Friday, December 13, 2013 3:23 PM
> To: Kwok, WingMan
> Cc: Balbi, Felipe; Shilimkar, Santosh; Linux USB Mailing List;
> kgene@samsung.com; Linux ARM Kernel Mailing List; linux-samsung-
> s...@vger.kernel.org; Linux OMAP Mailing List
Commit c952a8ba7136505cd1ca01735cc748ddc08c7d2f "usb: usbtest: add a
test case to support bos for queue control" will cause USB 2.01 and USB
2.10 devices with a BOS descriptor to fail case 15 of the control test.
The Link PM errata (released in 2007, updated in 2011) says:
"The value of the bcdUS
On Friday 13 December 2013 12:23 AM, David Cohen wrote:
> On Thu, Dec 12, 2013 at 07:25:55PM -0800, David Cohen wrote:
>> On Thu, Dec 12, 2013 at 09:01:04PM -0500, Santosh Shilimkar wrote:
>>> On Thursday 12 December 2013 08:51 PM, David Cohen wrote:
On Thu, Dec 12, 2013 at 08:06:24PM -0500, S
On Thursday 12 December 2013 07:43 PM, Felipe Balbi wrote:
> On Thu, Dec 12, 2013 at 07:29:24PM -0500, Santosh Shilimkar wrote:
>> On Thursday 12 December 2013 04:45 PM, Felipe Balbi wrote:
>>> A bare-minimum PM implementation which will
>>> server as building block for more complex
>> s/server/ser
On Tue, Nov 12, 2013 at 08:46:27AM +, Wang, Lin X wrote:
> Hi Sarah,
Hi Lin,
Sorry for taking so long to respond to this patch.
Yes, I think this is a bug, but the end result is harmless. Please send
an updated version of the patch to me, and Cc the linux-usb mailing
list.
> I found a pote
On Thu, Dec 12, 2013 at 06:37:28PM +, Ashwini Pahuja wrote:
> Hi Sarah,
>
> I am planning to use the UAS/streams feature under Linux, I know there
> were a lot of patches submitted by Hans in the last few weeks. Do you
> have any git repository from where I can pull the latest kernel with
> th
On Fri, 13 Dec 2013, James Bottomley wrote:
> On Fri, 2013-12-13 at 16:06 -0500, Alan Stern wrote:
> > On Fri, 13 Dec 2013, James Bottomley wrote:
> >
> > > Actually, I think I have this figured out. There's a thinko in one of
> > > the scsi_target_reap() cases. The original (and still existing
On Fri, Dec 13, 2013 at 05:55:20PM -0500, Santosh Shilimkar wrote:
> On Friday 13 December 2013 12:23 AM, David Cohen wrote:
> > On Thu, Dec 12, 2013 at 07:25:55PM -0800, David Cohen wrote:
> >> On Thu, Dec 12, 2013 at 09:01:04PM -0500, Santosh Shilimkar wrote:
> >>> On Thursday 12 December 2013 08
On Fri, 2013-12-13 at 19:48 -0500, Alan Stern wrote:
> On Fri, 13 Dec 2013, James Bottomley wrote:
>
> > On Fri, 2013-12-13 at 16:06 -0500, Alan Stern wrote:
> > > On Fri, 13 Dec 2013, James Bottomley wrote:
> > >
> > > > Actually, I think I have this figured out. There's a thinko in one of
> >
On Fri, 13 Dec 2013, James Bottomley wrote:
> > Sorry, but you're wrong. starget->reap_ref is _not_ incremented every
> > time we add a device to the target. That's one of the things we need to
> > fix.
>
> Well, then we would have a pretty astonishing cockup in the code. The
> found case of
This patch eliminates the reap_ref and replaces it with a proper kref.
On last put of this kref, the target is removed from visibility in
sysfs. The final call to scsi_target_reap() for the device is done from
__scsi_remove_device() and only if the device was made visible. This
ensures that the t
On Fri, 13 Dec 2013, James Bottomley wrote:
> This patch eliminates the reap_ref and replaces it with a proper kref.
> On last put of this kref, the target is removed from visibility in
> sysfs. The final call to scsi_target_reap() for the device is done from
> __scsi_remove_device() and only if
JZ4740 USB Device Controller is not OTG compatible and does not have DEVCTL
register in silicon.
During ethernet-over-usb transactions, on reset, musb driver tries to
read from DEVCTL and consequently sets device as host (A-Device)
instead of peripheral (B-Device), which makes it a composite devic
Hello,
Following the fix I submitted a few weeks ago, here is a set of
patches that add USB support for the Ingenic JZ4740 MIPS SoC.
The JZ4740 is found in the Ben NanoNote handheld computer which is
built by the Qi-Hardware community.
Even though Ben NanoNote is already supported in the kernel,
Add defconfig for the Ben NanoNote handheld computer which is built
around QI_LB60 board and Ingenic JZ4740 MIPS SoC.
Signed-off-by: Apelete Seketeli
---
arch/mips/configs/qi_lb60_defconfig | 188 +++
1 file changed, 188 insertions(+)
create mode 100644 arch/mip
Add support for Ingenic JZ4740 USB Device Controller through a
specific musb glue layer.
The platform data already available in tree for that USB Device
Controller was previously used by an out-of-tree USB gadget driver
which was not relying on the musb driver and was written by Ingenic
and the Qi
93 matches
Mail list logo
