Can any one let me know the difference in option and sierra kernel
modules ? looks like both drivers support GSM modem. And from the
source code perspective both look similar. I am able to load sierra
module for my Huawei USB dongle E156 and able to connect to internet
using pppd. Is it OK to use s
On Thu, Jan 29, 2015 at 10:37:34AM +0800, Peter Hung wrote:
> Hello.
>
> 1. For retry Issue:
>
> These patches is referenced from our other usb serial product. That
> product maybe not ack the control ep command when It's in very heavily
> loading. Our workaround is to modify driver to retry mo
Hello.
On 1/29/2015 5:01 AM, Peter Hung wrote:
Hello.
Please don't top-post.
I had using "scripts/checkpatch.pl -f" to scan original f81232.c.
It reported with "quoted string split across lines", so I merge these
2 strings into 1 in patch 1/5.
Seems like another unrelated change...
On some Intel MID platforms the ChipIdea USB controller is used. The EHCI PCI
is in conflict with the proper driver. The patch makes ehci-pci to be ignored
in favour of ChipIdea controller.
Acked-by: Alan Stern
Signed-off-by: Andy Shevchenko
---
drivers/usb/host/ehci-pci.c | 27
The patch series introduces the bypass_pci_id_table in ehci-pci to skip a probe
stage for certain devices.
Changes since v2:
- address Alex comments
- append Alan's ACK
Andy Shevchenko (2):
ehci-pci: disable for Intel MID platforms
chipidea: pci: add comment regarding to ehci-pci driver
dri
The patch points a developer of ChipIdea PCI driver to the bypass_pci_id_table
in ehci-pci driver. The table allows to skip a probe stage in ehci-pci for
certain IDs.
There is no functional change.
Signed-off-by: Andy Shevchenko
---
drivers/usb/chipidea/ci_hdrc_pci.c | 3 +++
1 file changed, 3
The patch joins the string literals for happy debugging. There is no functional
change.
Signed-off-by: Andy Shevchenko
---
drivers/usb/host/pci-quirks.c | 46 +++
1 file changed, 25 insertions(+), 21 deletions(-)
diff --git a/drivers/usb/host/pci-quirks.c
Chanwoo,
On 29/01/15 03:49, Chanwoo Choi wrote:
> Hi Roger,
>
> We need to discuss one point about 'id_irqwake'.
> I don't recommend to use 'id_irqwake' field.
>
> And I catch build warning by using "select" keywork in Kconfig.
> It is my wrong guide of "select" keyword. So, I'll change it
> as
On 28/01/15 19:09, Tony Lindgren wrote:
> * Roger Quadros [150128 04:15]:
>> On 28/01/15 04:19, Chanwoo Choi wrote:
I still fail to understand that we need to call disable_irq() in
.suspend() and
enable_irq() in .resume()
can you point me to any other drivers doing s
On Wed, Jan 28, 2015 at 10:47:18PM +0100, Arnd Bergmann wrote:
> The renesas usbhs driver calls extcon_get_edev_by_phandle(), which
> is defined in drivers/extcon/extcon-class.c, and that can be a
> loadable module. If the extcon-class support is disabled, usbhs
> will work correctly for all device
koelsch
and lager boards.
I noticed this problem while testing next-20150129.
I have provided boot logs at the end of this email.
>
> diff --git a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
> b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
> index b08c903..
On Wednesday 28 January 2015 13:26:03 Zubair Lutfullah Kakakhel wrote:
> + - clocks: Should contain a single clock specifier for the SoC UHC clock.
> + - clock-names: Must be "uhc"
>
Same comment as for the watchdog binding, this should probably be
removed. See what the other ohci drivers use and
> > > > > Can you share how tusb1210 is connected on the platform you're using
> > > > > as
> > > > > test for this patch? I don't think this driver would work reliably
> > > > > with
> > > > > this device:
> > > > > http://liliputing.com/2014/11/trekstor-launches-first-android-tablet-based-intel
On Wed, Jan 28, 2015 at 11:02:37PM -0600, Felipe Balbi wrote:
> Hi,
>
> On Fri, Jan 23, 2015 at 05:12:51PM +0200, Heikki Krogerus wrote:
> > @@ -6,4 +6,5 @@ obj-$(CONFIG_USB_COMMON) += usb-common.o
> > usb-common-y += common.o
> > usb-common-$(CONFIG_USB_LED_TRIG) +=
On Thu, Jan 29, 2015 at 02:50:13PM +0530, temp sha wrote:
> Can any one let me know the difference in option and sierra kernel
> modules ? looks like both drivers support GSM modem. And from the
> source code perspective both look similar. I am able to load sierra
> module for my Huawei USB dongle
> Also, I was chatting in private with David and, apparently, there's a
> way to request for eye diagram data from BIOS straight. That's more
> in-line with what we would do for DT-based boots, passing that
> eye-diagram data as a DT attribute.
>
> Care to comment ? If that's the case, I'd rather
On Wed, Jan 28, 2015 at 11:03:55PM -0600, Felipe Balbi wrote:
> On Fri, Jan 23, 2015 at 05:12:57PM +0200, Heikki Krogerus wrote:
> > ULPI PHYs need to be bound to their controllers with a
> > lookup. This adds helpers that the ULPI drivers can use to
> > do both, the registration of the PHY and the
On Thu, 29 Jan 2015, Peter Chen wrote:
> > > Then, it is strange. Do we need even two glue layer drivers for pci
> > > device? Look at usb/chipidea/ci_hdrc_pci.c it has pci_register_driver,
> > > and its host driver will call ehci_init_driver, it is definitely
> > > duplicated with usb/host/ehci-p
On Thu, 29 Jan 2015, Ruslan Bilovol wrote:
> Change behavior during registration of gadgets and
> gadget drivers in udc-core. Instead of previous
> approach when for successful probe of usb gadget driver
> at least one usb gadget should be already registered
> use another one where gadget drivers
On Thu, Jan 29, 2015 at 04:34:41PM +0200, Heikki Krogerus wrote:
> On Wed, Jan 28, 2015 at 11:03:55PM -0600, Felipe Balbi wrote:
> > On Fri, Jan 23, 2015 at 05:12:57PM +0200, Heikki Krogerus wrote:
> > > ULPI PHYs need to be bound to their controllers with a
> > > lookup. This adds helpers that the
On Thu, Jan 29, 2015 at 04:30:53PM +0200, Heikki Krogerus wrote:
> > Also, I was chatting in private with David and, apparently, there's a
> > way to request for eye diagram data from BIOS straight. That's more
> > in-line with what we would do for DT-based boots, passing that
> > eye-diagram data
Hi
On Thu, Jan 29, 2015 at 04:14:12PM +0200, Heikki Krogerus wrote:
> > > > > > Can you share how tusb1210 is connected on the platform you're
> > > > > > using as
> > > > > > test for this patch? I don't think this driver would work reliably
> > > > > > with
> > > > > > this device:
> > > > > >
On Tue, Jan 27, 2015 at 09:22:50AM -0600, Felipe Balbi wrote:
> Hi,
>
> On Sun, Jan 25, 2015 at 04:13:23PM +0800, Sneeker Yeh wrote:
> > These patches add support for XHCI compliant Host controller found
> > on Fujitsu Socs, and are based on http://lwn.net/Articles/629162/
> > The first patch is t
Hi,
Adding John
On Wed, Jan 28, 2015 at 10:49:00PM +0100, Arnd Bergmann wrote:
> It is currently possible to configure the dwc2 driver as built-in
> when host mode or dual-role is enabled, but the USB core is
> a loadable module. This leads to a link failure:
>
> drivers/built-in.o: In function
Linus ?
On Wed, Jan 28, 2015 at 07:54:44PM +0100, Robert Jarzmik wrote:
> Felipe Balbi writes:
>
> >> nop->gpiod_reset = devm_gpiod_get_optional(dev, "reset");
> >> if (gpiod_is_active_low(nop->gpiod_reset))
> >> gpiod_direction_output(nop->gpiod_reset, GPIOD_OUT_LOW)
The usbfs API has a peculiar hole: Users are not allowed to reap their
URBs after the device has been disconnected. There doesn't seem to be
any good reason for this; it is an ad-hoc inconsistency.
The patch allows users to issue the USBDEVFS_REAPURB and
USBDEVFS_REAPURBNDELAY ioctls (together wi
On 27.01.2015 14:12, Gunter Königsmann wrote:
> That's very good news indeed.
>
> Will re-run the tests on my scanner and looking forward to the fix entering
> mainline. In the meantime I can acknowledge that with the fix my computer
> accepts USB memory sticks that normally didn't work.
>
> Ki
On Wed, 28 Jan 2015, Joe Lawrence wrote:
> This one should have gone over to linux-usb.
>
> -- Joe
>
> On 01/28/2015 05:04 PM, Joe Lawrence wrote:
> > Hello linux-usb,
> >
> > We've hit a USB use-after-free on Stratus HW during device removal tests.
> > We're running fio disk I/O to a scsi disk
On Thu, 2015-01-29 at 11:29 -0500, Alan Stern wrote:
> The usbfs API has a peculiar hole: Users are not allowed to reap their
> URBs after the device has been disconnected. There doesn't seem to be
> any good reason for this; it is an ad-hoc inconsistency.
How many URBs can you queue this way?
On 27.01.2015 13:11, Heinz Diehl wrote:
> Hi,
>
> I'm not sure if this is the right place to report this, and would be glad if
> somebody could
> point me to the right one if I should be wrong.
>
> Anyway, since the main error message comes from xhci_hcd:
> When resuming from suspend to RAM, som
* Roger Quadros [150129 03:34]:
> On 28/01/15 19:09, Tony Lindgren wrote:
> > * Roger Quadros [150128 04:15]:
> >> On 28/01/15 04:19, Chanwoo Choi wrote:
>
> I still fail to understand that we need to call disable_irq() in
> .suspend() and
> enable_irq() in .resume()
>
>
Hi,
On 29-01-15 17:29, Alan Stern wrote:
The usbfs API has a peculiar hole: Users are not allowed to reap their
URBs after the device has been disconnected. There doesn't seem to be
any good reason for this; it is an ad-hoc inconsistency.
The patch allows users to issue the USBDEVFS_REAPURB an
On Thu, 29 Jan 2015, Oliver Neukum wrote:
> On Thu, 2015-01-29 at 11:29 -0500, Alan Stern wrote:
> > The usbfs API has a peculiar hole: Users are not allowed to reap their
> > URBs after the device has been disconnected. There doesn't seem to be
> > any good reason for this; it is an ad-hoc incon
Hi Heikki, Felipe,
On Thu, Jan 29, 2015 at 10:20:23AM -0600, Felipe Balbi wrote:
> Hi
>
> On Thu, Jan 29, 2015 at 04:14:12PM +0200, Heikki Krogerus wrote:
> > > > > > > Can you share how tusb1210 is connected on the platform you're
> > > > > > > using as
> > > > > > > test for this patch? I don'
On Thu, Jan 29, 2015 at 10:20:49AM -0600, Felipe Balbi wrote:
> On Thu, Jan 29, 2015 at 04:30:53PM +0200, Heikki Krogerus wrote:
> > > Also, I was chatting in private with David and, apparently, there's a
> > > way to request for eye diagram data from BIOS straight. That's more
> > > in-line with w
On 29.01.2015, Mathias Nyman wrote:
> > [ 274.156877] xhci_hcd :02:00.0: Host took too long to start, waited
> > 16000 microseconds.
> > [ 274.156896] xhci_hcd :02:00.0: PCI post-resume error -19!
> > [ 274.156897] xhci_hcd :02:00.0: HC died; cleaning up
> Does resume work withou
On Thu, Jan 29, 2015 at 10:04:16AM -0800, David Cohen wrote:
> On Thu, Jan 29, 2015 at 10:20:49AM -0600, Felipe Balbi wrote:
> > On Thu, Jan 29, 2015 at 04:30:53PM +0200, Heikki Krogerus wrote:
> > > > Also, I was chatting in private with David and, apparently, there's a
> > > > way to request for
On Thu, Jan 29, 2015 at 10:25:38AM -0800, David Cohen wrote:
> On Thu, Jan 29, 2015 at 10:04:16AM -0800, David Cohen wrote:
> > On Thu, Jan 29, 2015 at 10:20:49AM -0600, Felipe Balbi wrote:
> > > On Thu, Jan 29, 2015 at 04:30:53PM +0200, Heikki Krogerus wrote:
> > > > > Also, I was chatting in priv
On Thu, 2015-01-29 at 06:23 -0800, Greg KH wrote:
> On Thu, Jan 29, 2015 at 02:50:13PM +0530, temp sha wrote:
> > Can any one let me know the difference in option and sierra kernel
> > modules ? looks like both drivers support GSM modem. And from the
> > source code perspective both look similar. I
Currently the USB stack assumes that all host controller drivers are
capable of receiving wakeup requests from downstream devices.
However, this isn't true for the isp1760-hcd driver, which means that
it isn't safe to do a runtime suspend of any device attached to a
root-hub port if the device requ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Only in the hope that you might be able to do some additional magic
(but I won't be too disappointed if you tell that this time you have
already archieved enough) a fresh log for my scanner (that never
worked with USB-3.0 on my linux box and still do
Declare the interrupt as "one shot" so that it is masked until the end
of the threaded handler. This prevents the irq core from spitting out an
error :
"Threaded irq requested with handler=NULL and !ONESHOT for irq 63"
This was introduced by commit "usb: phy: generic: add vbus support".
Signed-
All the gpios, ie. reset-gpios and vbus-detect-gpio, should be optional
and not prevent the driver from working. Fix the regression in the
behavior introduced by commit "usb: phy: generic: migrate to gpio_desc".
Signed-off-by: Robert Jarzmik
---
Since v1: correctly handle the error codes
On Thu, Jan 29, 2015 at 8:41 PM, Robert Jarzmik wrote:
> + if (nop->gpiod_reset)
> + gpiod_direction_output(nop->gpiod_reset, 0);
Why do you set it to zero independently of the GPIO active level flag?
Previously, we had:
if (nop->reset_active_low)
gpio_f
On Tuesday, December 16, 2014 06:12:30 PM Octavian Purdila wrote:
> acpi_tb_delete_namespace_by_owner expects ACPI_MTX_INTERPRETER to be
> taken. This fixes the following issue:
>
> ACPI Error: Mutex [0x0] is not acquired, cannot release (20141107/utmutex-322)
> Call Trace:
> [] dump_stack+0x4f/
Hi Roger,
On 01/29/2015 08:26 PM, Roger Quadros wrote:
> Chanwoo,
>
> On 29/01/15 03:49, Chanwoo Choi wrote:
>> Hi Roger,
>>
>> We need to discuss one point about 'id_irqwake'.
>> I don't recommend to use 'id_irqwake' field.
>>
>> And I catch build warning by using "select" keywork in Kconfig.
>>
Hi Roger,
On 01/28/2015 09:15 PM, Roger Quadros wrote:
> This driver observes the USB ID pin connected over a GPIO and
> updates the USB cable extcon states accordingly.
>
> The existing GPIO extcon driver is not suitable for this purpose
> as it needs to be taught to understand USB cable states
According to the DWC2 datasheet, the HWCFG1 register stores
the configured endpoint directions for endpoints 0-15 in bit positions
0-31.
==
Endpoint Direction (EpDir)
This 32-bit field uses two bits per endpoint to determine the endpoint
direction.
Endpoint
Bits [31:30]: En
On Jan 29, 2015, at 8:42 AM, Mathias Nyman wrote:
> On 27.01.2015 14:12, Gunter Königsmann wrote:
>> That's very good news indeed.
>>
>> Will re-run the tests on my scanner and looking forward to the fix entering
>> mainline. In the meantime I can acknowledge that with the fix my computer
>> ac
On 01/28/2015 11:26 PM, Kaukab, Yousaf wrote:
>
>> -Original Message-
>> From: John Youn [mailto:john.y...@synopsys.com]
>> Sent: Thursday, January 29, 2015 3:25 AM
>> To: Kaukab, Yousaf; linux-usb@vger.kernel.org; ba...@ti.com;
>> john.y...@synopsys.com
>> Cc: Herrero, Gregory; r.bald...@
R_PTR(-ENODEV)).
- So, I will write a patch to set tx_chan and rx_chan to NULL in the
usbhsf_dma_init_dt()
if these values are IS_ERR.
Best regards,
Yoshihiro Shimoda
> I noticed this problem while testing next-20150129.
>
> I have provided boot logs at the end of this email
On 01/29/2015 08:25 AM, Felipe Balbi wrote:
> Hi,
>
> Adding John
>
> On Wed, Jan 28, 2015 at 10:49:00PM +0100, Arnd Bergmann wrote:
>> It is currently possible to configure the dwc2 driver as built-in
>> when host mode or dual-role is enabled, but the USB core is
>> a loadable module. This leads
On 01/28/2015 02:02 AM, Antti Seppälä wrote:
> On 27 January 2015 at 04:18, John Youn wrote:
>>> From: Vincent Pelletier [mailto:plr.vinc...@gmail.com]
>>> Sent: Friday, January 23, 2015 12:19 AM
>>>
>>> On Fri, 23 Jan 2015 02:38:37 +, John Youn
>>> wrote:
Having the __raw functions ever
On Thu, Jan 29, 2015 at 05:29:23PM -0800, John Youn wrote:
> On 01/28/2015 11:26 PM, Kaukab, Yousaf wrote:
> >
> >> -Original Message-
> >> From: John Youn [mailto:john.y...@synopsys.com]
> >> Sent: Thursday, January 29, 2015 3:25 AM
> >> To: Kaukab, Yousaf; linux-usb@vger.kernel.org; ba..
Set correct product type from 16654 to 16550A and
fix the ioctl TIOCGSERIAL return struct values.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
The original driver had do not any h/w change in driver.
This patch implements with configure H/W for
baud/parity/word length/stop bits functional.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 144 +---
1 file changed, 137 insertions(+), 7 d
This patch implement relative MCR/MSR function, such like
tiocmget()/tiocmset()/dtr_rts().
The update_mctrl() replace set_control_lines() to do MCR control
so we clean-up the set_control_lines() function.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 105 ++
The F81232 interrupt ep will continuously report IIR register value.
We had implement the interrupt callback to read IIR, If noticed with
MSR change, we will call worker to read MSR later.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 114 +--
The F81232 bulk-in is RX data channel. Data format is
[LSR+Data][LSR+Data]. , We had reimplemented in this patch.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 47 +++--
1 file changed, 15 insertions(+), 32 deletions(-)
diff --git a/driv
The F81232 real bulk-in/out ep buffer size is 64Bytes
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index c5dc233..4f42e9d 100644
--- a/drivers/usb/serial
add co-author and fix no '>' in greg kh's email
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index 4f42e9d..9ef9775 100644
--- a/drivers/usb/serial/f81232.
On Thu, Jan 29, 2015 at 10:44:48AM -0500, Alan Stern wrote:
> On Thu, 29 Jan 2015, Peter Chen wrote:
>
> > > > Then, it is strange. Do we need even two glue layer drivers for pci
> > > > device? Look at usb/chipidea/ci_hdrc_pci.c it has pci_register_driver,
> > > > and its host driver will call eh
This patch fixes an issue that the following commit causes NULL
pointer dereference in dma_release_channel().
"usb: renesas_usbhs: add support for requesting DT DMA"
(commit id abd2dbf6bb1b5f3a03a8c76b1a8879da1dd30caa)
The usbhsf_dma_init_dt() should set fifo->{t,r}x_chan to NULL if
dma_request_
63 matches
Mail list logo
