On 04/29/2014 07:16 PM, Felipe Balbi wrote:
> On Tue, Apr 29, 2014 at 11:14:20AM -0500, Felipe Balbi wrote:
>> On Tue, Apr 29, 2014 at 10:50:39AM +0300, Roger Quadros wrote:
>>> +Nishant
>>>
>>> Hi,
>>>
>>> On 04/28/2014 07:03 PM, Felipe Balbi wrote:
Hi,
On Mon, Apr 28, 2014 at 05:01
Add required device node for ehci and ohci controllers to
enable USB 2.0 support.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
b/arch
Add required device node for usb2phy to let enable USB 2.0
support.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
b/arch/arm/boot/dts/exynos5420.dtsi
index cfa3755..16b860a 10
From: Kamil Debski
Add support to PHY of USB2 of the Exynos 5250 SoC.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split the usb phy entries from
syscon entries from earlier patch: dts: Add usb2phy to Exynos 5250]
[gautam.vi...@samsung.com: Added phy entry for OHCI also along with EHC
This patch adds sysreg-syscon node to exynos5250 and exynos5420 device
tree, to access System Register's registers using syscon driver.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split this syreg-syscon dts entry from
dts: Add usb2phy to Exynos 5250 patch]
[gautam.vi...@samsung.com: a
Next version for earlier patch-series:
[PATCH v7 0/2] dts: Add usb2phy to Exynos 5250
Based on 'for-next' branch of Kgene's linux-samsung tree.
Tested with driver side patches:
[PATCH v2 1/4] usb: ohci-exynos: Use struct device instead of platform_device
[PATCH v2 2/4] usb: ehci-exynos: Use struc
Thank you Alan,
here you go: http://pastebin.com/txu8M68L we included the register file
both before and after the hangup, with a 1s interval.
Matteo
Il 25/04/2014 18:29, Alan Stern ha scritto:
On Thu, 24 Apr 2014, Matteo Fortini wrote:
After some time, we finally had another hangup on kern
Hi Vivek,
On 04/30/14 14:25, Vivek Gautam wrote:
> Add required device node for usb2phy to let enable USB 2.0
> support.
>
> Signed-off-by: Vivek Gautam
> ---
> arch/arm/boot/dts/exynos5420.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5420
Hi Arun,
On Wed, Apr 30, 2014 at 3:55 PM, Arun Kumar K wrote:
> Hi Vivek,
>
> On 04/30/14 14:25, Vivek Gautam wrote:
>> Add required device node for usb2phy to let enable USB 2.0
>> support.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>> arch/arm/boot/dts/exynos5420.dtsi | 10 ++
>> 1 f
On Tue, 29 Apr 2014, Dan Williams wrote:
> > What happens if a thread tries to resume or suspend a port while the
> > hub is being reset? With nothing to prevent it, the request sent to
> > the hub will fail and the port may end up in a runtime PM error state.
> >
>
> I'm expected to be protecte
On Tue, Apr 29, 2014 at 11:16 AM, Felipe Balbi wrote:
> On Tue, Apr 29, 2014 at 11:14:20AM -0500, Felipe Balbi wrote:
>> On Tue, Apr 29, 2014 at 10:50:39AM +0300, Roger Quadros wrote:
>> > +Nishant
>> >
>> > Hi,
>> >
>> > On 04/28/2014 07:03 PM, Felipe Balbi wrote:
>> > > Hi,
>> > >
>> > > On Mon,
On Fri, Mar 14, 2014 at 11:41:47AM -0400, Alan Stern wrote:
> On Fri, 14 Mar 2014, Amit Virdi wrote:
>
> > Felipe, Alan,
> >
> > On 2/25/2014 10:43 AM, Amit Virdi wrote:
> > > ccing: Felipe Balbi, Alen Stern
> > >
> > > On 2/24/2014 3:55 PM, Amit VIRDI wrote:
> > >> Interrupt endpoints behave qui
On Thu, Apr 24, 2014 at 12:54:13PM +0400, Paul Fertser wrote:
> If VBUS is already present during the driver initialisation, the
s/initialisation/initialization
> corresponding IRQ never fires, so there is no way the gadget can get
> enumerated.
>
> This patch is real-life tested on an i.MX25 bo
On Mon, Apr 28, 2014 at 06:46:01PM +0530, Pratyush Anand wrote:
> On Sat, Apr 26, 2014 at 02:10:21AM +0800, Felipe Balbi wrote:
> > On Fri, Apr 25, 2014 at 02:27:11PM +0530, Pratyush Anand wrote:
> > > On Tue, Apr 22, 2014 at 10:41:06PM +0800, Felipe Balbi wrote:
> > > > On Tue, Apr 22, 2014 at 10:
Hi,
On Mon, Apr 28, 2014 at 04:34:17PM +0300, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
> Allow support to use 2nd HSPHY with USB2 Core.
> Some platforms may have configuration to allow USB controller
> work with any of the two HSPHYs present. By default driver
> configures USB core to us
On Mon, Apr 28, 2014 at 04:34:20PM +0300, Ivan T. Ivanov wrote:
> From: Tim Bird
>
> Select the secondary PHY using the TCSR register, if phy-num=1
> in the DTS (or phy_number is set in the platform data). The
> SOC has 2 PHYs which can be used with the OTG port, and this
> code allows configuri
On Thu, Apr 24, 2014 at 06:48:11PM +0300, Ivan T. Ivanov wrote:
> From: Tim Bird
>
> Fix the value used for Parallel Transceiver Select (PTS) for the MSM USB
> controller. This is a standard chipidea PORTSC definition, where
> a PHY_TYPE of 10b (<<30) is ULPI and 11b (<<30) is SERIAL.
> Fix the
On Thu, Apr 24, 2014 at 11:17:11AM +0200, Andrzej Pietrasiewicz wrote:
> There is a custom (non-USB IF) extension to the USB standard:
>
> http://msdn.microsoft.com/library/windows/hardware/gg463182
>
> The said extension is maintained by Microsoft for Microsoft.
>
> Yet it is fairly common
By adding COMPILE_TEST to the list of dependencies
we can build test this driver on all other architectures
which is very valuable for maintainers applying patches
and to find silly mistakes during development.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/Kconfig | 2 +-
1 file changed, 1 ins
this solves the following build warning found when
running compile tests.
drivers/usb/phy/phy-msm-usb.c: In function ‘msm_otg_read_dt’:
drivers/usb/phy/phy-msm-usb.c:1459:20: warning: cast from pointer \
to integer of different size [-Wpointer-to-int-cast]
pdata->phy_type = (int) id->dat
Remove that single instance of writel_relaxed()
call which is only available on ARM architecture.
This will let us build test this driver on all
different architectures.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/phy-msm-usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
Hi Vivek,
On 30 April 2014 14:25, Vivek Gautam wrote:
> From: Kamil Debski
>
> Add support to PHY of USB2 of the Exynos 5250 SoC.
>
> Signed-off-by: Kamil Debski
> [gautam.vi...@samsung.com: Split the usb phy entries from
> syscon entries from earlier patch: dts: Add usb2phy to Exynos 5250]
> [
On 30 April 2014 14:25, Vivek Gautam wrote:
> Add required device node for ehci and ohci controllers to
> enable USB 2.0 support.
>
> Signed-off-by: Vivek Gautam
> ---
> arch/arm/boot/dts/exynos5420.dtsi | 36 +++-
> 1 file changed, 35 insertions(+), 1 deletion(
hi,
On Mon, Apr 28, 2014 at 03:14:59PM +0200, Robert Baldyga wrote:
> Hi Felipe,
>
> Are you going to merge this examples, or should they be merged through
> another tree?
I suppose Greg has been taking tools directly. Greg, do you want me to
include this in my pull request ?
--
balbi
signat
On Thu, Apr 10, 2014 at 03:41:16PM +0200, Stefan Roese wrote:
> Hi Felipe,
>
> On 08.04.2014 16:31, Felipe Balbi wrote:
> >>> diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
> >>> index 819a7cd..d369bf1 100644
> >>> --- a/drivers/usb/musb/omap2430.c
> >>> +++ b/drivers/usb/m
Hi,
On Wed, Apr 23, 2014 at 09:57:52AM +0530, sundeep subbaraya wrote:
> >> > I get the impression that the two of you are arguing past each other.
> >> > It appears that Sundeep is talking about transferring data from the
> >> > gadget driver's buffer to an internal buffer in the UDC hardware, bu
On Tue, Apr 15, 2014 at 10:18:09AM +0200, Robert Baldyga wrote:
> Hi Felipe,
>
> > >> On 04/02/2014 10:47 AM, Peter Chen wrote:
> > >>> We have historic problem that the gadget will not work if the gadget
> > >>> is build-in and the udc driver is defered probe due to some
> > >>> resources are not
On Tue, Apr 22, 2014 at 12:56:31PM -0700, ian coolidge wrote:
> Hi,
>
> Thanks for your response, I found a fix in 3.9-rc1,
> commit bb3a2ef2eb8cfaea335dcb3426350df7f3d48069 from Supriya Karanth:
>
> usb: musb: set TXMAXP and AUTOSET for full speed bulk in device mode
>
> I was able to back port
Hi,
On Tue, Apr 29, 2014 at 11:10:42AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Tue, Apr 29, 2014 at 05:21:42PM -0400, Zhuang Jin Can wrote:
> > On Mon, Apr 28, 2014 at 10:55:36AM -0500, Felipe Balbi wrote:
> > > On Mon, Apr 28, 2014 at 04:49:23PM -0400, Zhuang Jin Can wrote:
> > > > Adds a debugf
Hi Greg,
here's my second pull request for this -rc cycle.
Please consider merging to your usb-linux branch.
cheers
The following changes since commit a31a942a148e0083ce560ffeb54fb60e06ab7201:
usb: phy: am335x-control: wait 1ms after power-up transitions (2014-04-21
10:21:24 -0500)
are ava
Hi,
On Thu, May 01, 2014 at 01:06:25AM -0400, Zhuang Jin Can wrote:
> Hi,
>
> On Tue, Apr 29, 2014 at 11:10:42AM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Apr 29, 2014 at 05:21:42PM -0400, Zhuang Jin Can wrote:
> > > On Mon, Apr 28, 2014 at 10:55:36AM -0500, Felipe Balbi wrote:
> > > >
On Thu, Apr 24, 2014 at 11:17:13AM +0200, Andrzej Pietrasiewicz wrote:
> There is a custom (non-USB IF) extension to the USB standard:
>
> http://msdn.microsoft.com/library/windows/hardware/gg463182
>
> The said extension is maintained by Microsoft for Microsoft.
>
> Yet it is fairly common for
On Wed, Apr 30, 2014 at 12:14:42PM -0500, Felipe Balbi wrote:
> sorry but your patch is not good for acceptance in mainline.
>
Thanks your time.
Jincan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo i
On Wed, 30 Apr 2014, Felipe Balbi wrote:
> > We still have unsolved problem with deferred probe in UDC drivers, so
> > there is real need for some fixes.
>
> sure, we do need a fix, but it's very difficult to know when we can
> allow for gadget drivers to be loaded. Think of it this way:
>
> say
On Wed, Apr 30, 2014 at 01:43:35PM -0400, Alan Stern wrote:
> On Wed, 30 Apr 2014, Felipe Balbi wrote:
>
> > > We still have unsolved problem with deferred probe in UDC drivers, so
> > > there is real need for some fixes.
> >
> > sure, we do need a fix, but it's very difficult to know when we can
Signed-off-by:Tim Bird
Sent from my Sony Xperia™ smartphone
Felipe Balbi wrote
>On Thu, Apr 24, 2014 at 06:48:11PM +0300, Ivan T. Ivanov wrote:
>> From: Tim Bird
>>
>> Fix the value used for Parallel Transceiver Select (PTS) for the MSM USB
>> controller. This is a standard chipide
The kernel being used is 3.5.0-17-generic.
I'm working with a device for which this operation is known to work on Windows.
When I use usbfs, however, the bulk input transfer is yielding ETIME (error
62). This is true both synchronously (using ioctl[USBDEVFS_BULK]) and
asynchronously (in which c
At least we should giveback the current request to the
gadget. Otherwise, the gadget will be stuck without knowing
anything.
It was oberved that the failure can happen if the request is
queued when the run/stop bit of controller is not set.
Signed-off-by: Zhuang Jin Can
---
drivers/usb/dwc3/gad
On Wed, 2014-04-30 at 10:04 -0400, Alan Stern wrote:
> On Tue, 29 Apr 2014, Dan Williams wrote:
>
> > > What happens if a thread tries to resume or suspend a port while the
> > > hub is being reset? With nothing to prevent it, the request sent to
> > > the hub will fail and the port may end up in
endpoint.maxburst may be 0 if a gadget doesn't call config_ep_by_speed()
to update it from the companion descriptor.
And endpoint.maxburst - 1 returns 1b which wrongly sets bit
26 of endpoint parameter 0.
This sets a wrong endpoint state and will cause "Get Endpoint State"
command can't get the
On Wed, Apr 30, 2014 at 11:45:41AM -0500, Felipe Balbi wrote:
> hi,
>
> On Mon, Apr 28, 2014 at 03:14:59PM +0200, Robert Baldyga wrote:
> > Hi Felipe,
> >
> > Are you going to merge this examples, or should they be merged through
> > another tree?
>
> I suppose Greg has been taking tools directl
Hello,
Thank you for the review.
On Wed, Apr 30, 2014 at 11:06:25AM -0500, Felipe Balbi wrote:
> On Thu, Apr 24, 2014 at 12:54:13PM +0400, Paul Fertser wrote:
> > If VBUS is already present during the driver initialisation, the
>
> s/initialisation/initialization
If I'm understanding [1] proper
On Wed, 30 Apr 2014, Felipe Balbi wrote:
> > > Now say you want to use that gadget driver which is deferred, you unload
> > > first gadget driver and then nothing happens because you have no way to
> > > tell that gadget driver that you want it to bind to the UDC which is now
> > > available.
> >
On Wed, Apr 23, 2014 at 10:53 PM, Peter Chen wrote:
>
>
>>
>> On Wed, Apr 23, 2014 at 10:30 PM, Peter Chen
>> wrote:
>>
>> > Oh, sorry. I forget to send it to Greg yesterday. If you can wait, I
>> > will send it next time (within two weeks) with other patches, if
>> > can't, I can send it today.
On Wed, 30 Apr 2014, Dan Williams wrote:
> On Wed, 2014-04-30 at 10:04 -0400, Alan Stern wrote:
> > On Tue, 29 Apr 2014, Dan Williams wrote:
> >
> > > > What happens if a thread tries to resume or suspend a port while the
> > > > hub is being reset? With nothing to prevent it, the request sent t
Hi,
On Thu, May 01, 2014 at 02:36:08AM -0400, Zhuang Jin Can wrote:
> At least we should giveback the current request to the
> gadget. Otherwise, the gadget will be stuck without knowing
> anything.
>
> It was oberved that the failure can happen if the request is
> queued when the run/stop bit of
On Wed, 30 Apr 2014, Dave Mielke wrote:
> The kernel being used is 3.5.0-17-generic.
Have you tried 3.14? 3.5 is getting old.
> I'm working with a device for which this operation is known to work on
> Windows.
What operation?
> When I use usbfs, however, the bulk input transfer is yielding
On Thu, May 01, 2014 at 03:16:04AM -0400, Zhuang Jin Can wrote:
> endpoint.maxburst may be 0 if a gadget doesn't call config_ep_by_speed()
> to update it from the companion descriptor.
> And endpoint.maxburst - 1 returns 1b which wrongly sets bit
> 26 of endpoint parameter 0.
> This sets a wron
On Wed, Apr 30, 2014 at 03:41:48PM -0400, Alan Stern wrote:
> On Wed, 30 Apr 2014, Felipe Balbi wrote:
>
> > > > Now say you want to use that gadget driver which is deferred, you unload
> > > > first gadget driver and then nothing happens because you have no way to
> > > > tell that gadget driver
On Wed, Apr 30, 2014 at 12:17:28PM -0700, Greg KH wrote:
> On Wed, Apr 30, 2014 at 11:45:41AM -0500, Felipe Balbi wrote:
> > hi,
> >
> > On Mon, Apr 28, 2014 at 03:14:59PM +0200, Robert Baldyga wrote:
> > > Hi Felipe,
> > >
> > > Are you going to merge this examples, or should they be merged thro
+Suresh
(top-posting, yeah yeah :-)
On Wed, Apr 30, 2014 at 11:27:45PM +0400, Paul Fertser wrote:
> Hello,
>
> Thank you for the review.
>
> On Wed, Apr 30, 2014 at 11:06:25AM -0500, Felipe Balbi wrote:
> > On Thu, Apr 24, 2014 at 12:54:13PM +0400, Paul Fertser wrote:
> > > If VBUS is already p
Hi,
On Wed, Apr 30, 2014 at 08:07:05PM +0200, Bird, Tim wrote:
> Signed-off-by:Tim Bird
thanks Tim but I already had your SoB in the patch, I need Ivan's :-)
>
> Sent from my Sony Xperia™ smartphone
>
> Felipe Balbi wrote
>
> >On Thu, Apr 24, 2014 at 06:48:11PM +0300, Ivan T. Ivano
Am 2014-04-30 22:12, schrieb Eduard Hasenleithner:
> As Thomas Schäfer reported, the E5776 does not work anymore with kernel
> 3.13. I bisected the problem and found commit
> 6a9612e2cb22b3fd6a7304dcbf2b4ee1cf2104b2
> being the first bad commit.
>
> Does this give you already enough hints on
On Wed, 30 Apr 2014, Matteo Fortini wrote:
> Thank you Alan,
> here you go: http://pastebin.com/txu8M68L we included the register file
> both before and after the hangup, with a 1s interval.
Thanks. This confirms the reason for the problem. It's a hardware bug
in the OHCI controller; after com
Hi Bjørn.
As Thomas Schäfer reported, the E5776 does not work anymore with kernel
3.13. I bisected the problem and found commit
6a9612e2cb22b3fd6a7304dcbf2b4ee1cf2104b2
being the first bad commit.
Does this give you already enough hints on what goes wrong, or do I need
to focus the proble
[quoted lines by Alan Stern on 2014/04/30 at 16:00 -0400]
>Have you tried 3.14? 3.5 is getting old.
That's somewhat beyond my control. I'm logged in remotely to a system which
doesn't belong to me but which is where the device is. It's also a holiday
there, so, even if the owner is willing to
On Tue, 29 Apr 2014, Peter Münster wrote:
> On Tue, Apr 29 2014, Alan Stern wrote:
>
> > It's noticeable that your logs include resets of the affected devices,
> > whereas the older kernels did not need any resets. This suggests that
> > these OHCI controllers will always have problems with glob
Aha, I'm already more than one month late since it is already fixed in
commit ff0992e9036e9810e7cd45234fa32ca1e79750e2. I wonder why google did
not bring up any information about the fix when searching for e5776.
Eduard
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the
Great, thank you!
Just tell me if you need any help.
Matteo
Il 30/04/2014 22:29, Alan Stern ha scritto:
On Wed, 30 Apr 2014, Matteo Fortini wrote:
Thank you Alan,
here you go: http://pastebin.com/txu8M68L we included the register file
both before and after the hangup, with a 1s interval.
Th
On Wed, 2014-04-30 at 15:51 -0400, Alan Stern wrote:
> On Wed, 30 Apr 2014, Dan Williams wrote:
>
> > On Wed, 2014-04-30 at 10:04 -0400, Alan Stern wrote:
> > > On Tue, 29 Apr 2014, Dan Williams wrote:
> > >
> > > > > What happens if a thread tries to resume or suspend a port while the
> > > > >
Hi Mathias,
I tested both this patch and your global command queue patches on top of
your for-usb-linus branch. After reverting commit 400362f1d8dc "ALSA:
usb-audio: Resume mixer values properly", I was able to get my USB
webcam working. [1]
I wrote a small shell script (attached) to start and k
Hi,
On Wed, Apr 30, 2014 at 04:04:24PM -0700, Sarah Sharp wrote:
> Hi Mathias,
>
> I tested both this patch and your global command queue patches on top of
> your for-usb-linus branch. After reverting commit 400362f1d8dc "ALSA:
> usb-audio: Resume mixer values properly", I was able to get my USB
Script is attached now.
Sarah
On Wed, Apr 30, 2014 at 04:04:24PM -0700, Sarah Sharp wrote:
> Hi Mathias,
>
> I tested both this patch and your global command queue patches on top of
> your for-usb-linus branch. After reverting commit 400362f1d8dc "ALSA:
> usb-audio: Resume mixer values properly
On Thu, Apr 24 2014, Andrzej Pietrasiewicz wrote:
> Variable Length Array macros allow portable (compilable with both gcc
> and clang) way of allocating a number of structures using a single
> memory chunk. They can be useful for files other than f_fs.c,
> so move them to a header file.
>
> Signed-
On Thu, Apr 24 2014, Andrzej Pietrasiewicz wrote:
> There is a custom (non-USB IF) extension to the USB standard:
>
> http://msdn.microsoft.com/library/windows/hardware/gg463182
>
> The said extension is maintained by Microsoft for Microsoft.
>
> Yet it is fairly common for various devices to use i
On Thu, Apr 24 2014, Andrzej Pietrasiewicz wrote:
> @@ -438,8 +440,46 @@ static int config_desc(struct usb_composite_dev *cdev,
> unsigned w_value)
>
> }
>
> - /* This is a lookup by config *INDEX* */
> w_value &= 0xff;
> + /*
> + * This is a lookup to make non-complia
On Thu, Apr 24 2014, Andrzej Pietrasiewicz wrote:
> In order for usb functions to expose OS descriptors they
> need to be made aware of OS descriptors. This involves
> extending the "options" structure and setting up
> appropriate associations.
>
> Signed-off-by: Andrzej Pietrasiewicz
> ---
> dri
On Wed, Apr 30 2014, Felipe Balbi wrote:
> are you sure there isn't some crappy patent from MS which would
> prevent us from implementing this ?
Should that stop us? Especially since not knowing is arguably a good
strategy as one can argue unwillful infringement. Just my opinion.
--
Best regar
On 4/30/2014 9:36 PM, Felipe Balbi wrote:
On Fri, Mar 14, 2014 at 11:41:47AM -0400, Alan Stern wrote:
On Fri, 14 Mar 2014, Amit Virdi wrote:
Felipe, Alan,
On 2/25/2014 10:43 AM, Amit Virdi wrote:
ccing: Felipe Balbi, Alen Stern
On 2/24/2014 3:55 PM, Amit VIRDI wrote:
Interrupt endpoints be
69 matches
Mail list logo
