Hi,
On 01-06-15 20:34, Felipe Balbi wrote:
On Mon, Jun 01, 2015 at 11:30:45AM -0700, Hans de Goede wrote:
Hi,
On Sunday, May 31, 2015 at 6:10:32 PM UTC+2, Hans de Goede wrote:
Hi Kishon & Felipe,
Here is an updated version of the remaining (not yet merged in Felipe's
tree)
sunxi musb patche
On Mon, 2015-06-01 at 18:14 -0700, Laura Abbott wrote:
> Bluetooth devices off of some buses such as USB may lose power across
> suspend/resume. When this happens, drivers may need to have the setup
> function called again and behave differently than a cold power on.
Yes, but what is the point? We
ATOL FPrint fiscal printers require usb_clear_halt to be executed
to work properly. Add quirk to fix the issue.
Signed-off-by: Alexey Sokolov
---
drivers/usb/class/cdc-acm.c | 9 +
drivers/usb/class/cdc-acm.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/usb/class/cdc-ac
On 02/06/15 11:05, Alexey Sokolov wrote:
> ATOL FPrint fiscal printers require usb_clear_halt to be executed
> to work properly. Add quirk to fix the issue.
>
> Signed-off-by: Alexey Sokolov
> ---
> drivers/usb/class/cdc-acm.c | 9 +
> drivers/usb/class/cdc-acm.h | 1 +
> 2 files changed
On Tue, 2015-06-02 at 11:05 +0300, Alexey Sokolov wrote:
> ATOL FPrint fiscal printers require usb_clear_halt to be executed
> to work properly. Add quirk to fix the issue.
>
Hi,
thank you for this patch.
> Signed-off-by: Alexey Sokolov
> ---
> drivers/usb/class/cdc-acm.c | 9 +
> dr
On Mon, May 25, 2015 at 4:53 PM, Tomeu Vizoso
wrote:
> have looked into ordered probing as a
> better way of solving this than moving nodes around in the DT or playing with
> initcall levels.
>
> While reading the thread [1] that Alexander Holler started with his series to
> make probing order de
ATOL FPrint fiscal printers require usb_clear_halt to be executed
to work properly. Add quirk to fix the issue.
Signed-off-by: Alexey Sokolov
---
drivers/usb/class/cdc-acm.c | 9 +
drivers/usb/class/cdc-acm.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/usb/class/cdc-ac
I changed my mind, and decided to try in following this new way.
This series splits the cdc_ncm_ndp function in two parts:
- one that finds NDP blocks already present in the SKB being sent out
- one that pushes new ones, starting from where the _find function left.
After this splitting it seems mo
Split this function in two new ones:
- cdc_ncm_ndp16_find: finds an NDP block in the chain mathcing a supplied
signature; a pointer to it is returned in case of success;
- cdc_ncm_ndp16_push: create and add to skb a new NDP block;
cdc_ncm_ndp16_push refers to the last NDP visited by cdc_ncm_ndp1
This is useful to split up the cdc_ncm_ndp function later on.
The resulting code will be anyway stateful.
Signed-Off-By: Enrico Mioso
---
include/linux/usb/cdc_ncm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/usb/cdc_ncm.h b/include/linux/usb/cdc_ncm.h
index 7c9b484..91722
Yes, I gone through this warning. It is because if i want to make this
compilation warning free
than i have to change the prototype of a open function pointer
described in usb_serial_driver
and changing the prototype over there would affect all the device
driver lying in usb-serial
category , which
[ Please avoid top-posting. ]
On Tue, Jun 02, 2015 at 02:49:30PM +0530, Abhishek bist wrote:
> Yes, I gone through this warning. It is because if i want to make this
> compilation warning free
> than i have to change the prototype of a open function pointer
> described in usb_serial_driver
> and c
On 2 June 2015 at 10:48, Linus Walleij wrote:
> On Mon, May 25, 2015 at 4:53 PM, Tomeu Vizoso
> wrote:
>
>> have looked into ordered probing as a
>> better way of solving this than moving nodes around in the DT or playing with
>> initcall levels.
>>
>> While reading the thread [1] that Alexander
Hi
On 29.05.2015 15:35, Ralf Jung wrote:
> Hi again,
>
>> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
>> fixes the problem: When I subsequently plug in the disk, it is
>> recognized correctly. I confirmed this with an older kernel (the 3.16
>> Debian kernel, to be mor
Hi,
>>> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control"
>>> fixes the problem: When I subsequently plug in the disk, it is
>>> recognized correctly. I confirmed this with an older kernel (the 3.16
>>> Debian kernel, to be more precise). That's good to know, now I don't
>>>
On recent Qualcomm platforms VBUS and ID lines are not routed to
USB PHY LINK controller. Use extcon framework to receive connect
and disconnect ID and VBUS notification.
Signed-off-by: Ivan T. Ivanov
---
Changes sice v2 [1].
* Simulate IRQ on extcon event - used to trigger OTG state machine.
I
On Sat, May 30, 2015 at 10:29 PM, Grant Likely
wrote:
> On Mon, Jul 7, 2014 at 6:31 PM, Greg Kroah-Hartman
> wrote:
>>> However is the MFD cell approach acceptable?
>>
>> Yes it is.
>
> Going back to this old conversation... Actually, I disagree. There is
> absolutely no need to go the MFD appro
On Mon, Jun 1, 2015 at 9:28 PM, Marcel Holtmann wrote:
> Hi Laura,
>
>> Bluetooth devices off of some buses such as USB may lose power across
>> suspend/resume. When this happens, drivers may need to have the setup
>> function called again and behave differently than a cold power on.
>> Add a rese
Hi,
On Tue, Jun 02, 2015 at 09:14:05AM +0200, Hans de Goede wrote:
> >>>Here is an updated version of the remaining (not yet merged in Felipe's
> >>>tree)
> >>>sunxi musb patches.
> >>>
> >>>The "phy-sun4i-usb: Add full support for usb0 phy / OTG" patch has been
> >>>updated with a small bug-fix a
On Sun, May 31, 2015 at 06:10:26PM +0200, Hans de Goede wrote:
> This is based on initial code to get the Allwinner sunxi musb controller
> supported by Chen-Yu Tsai and Roman Byshko.
>
> This adds support for the Allwinner sunxi musb controller in both host only
> and otg mode. Peripheral only mo
Hi Josh,
>>> Bluetooth devices off of some buses such as USB may lose power across
>>> suspend/resume. When this happens, drivers may need to have the setup
>>> function called again and behave differently than a cold power on.
>>> Add a reset_resume function for drivers to call. During the
>>> re
Hello. I have got "Asus Z87-Expert" motherboard with integrated
bluetooth adapter. It causes the following error on boot:
"usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409"
Though there are no real problems with bluetooth, this error is annoying.
Here is some information:
Hi,
On Mon, Jun 01, 2015 at 11:28:23AM +0200, Hans de Goede wrote:
> On 01-06-15 11:22, Maxime Ripard wrote:
> >On Sun, May 31, 2015 at 06:10:25PM +0200, Hans de Goede wrote:
> >>+ /* We either want both gpio pins or neither (when in host mode) */
> >>+ if (!data->id_det_gpio != !data->vbus_de
On Monday 01 June 2015 16:51:30 Sergei Shtylyov wrote:
> Hello.
>
> On 6/1/2015 1:43 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > If kzalloc returns null then isp1760_ep_alloc_request performs
> > a null pointer dereference on req. Check for null to avoid this.
>
> I told you there's
Hello.
On 06/02/2015 06:41 PM, Laurent Pinchart wrote:
From: Colin Ian King
If kzalloc returns null then isp1760_ep_alloc_request performs
a null pointer dereference on req. Check for null to avoid this.
I told you there's no dereference and yet you're repeating it again. :-(
How abou
On Tue, 2 Jun 2015, Alexander wrote:
> Hello. I have got "Asus Z87-Expert" motherboard with integrated
> bluetooth adapter. It causes the following error on boot:
> "usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409"
This means the bluetooth adapter sent an invalid string
From: Colin Ian King
isp1760_ep_alloc_request allocates a structure with kzalloc without checking
for NULL and then returns a pointer to one of the structure fields. As the
field happens to be the first in the structure the caller can properly check
for NULL, but this is risky if the structure
I have never seen any bcma device with an USB host core which was not a
SoC, the bcma devices have an USB device core with a different core id.
Some SoC have IDs with 47XX and 53XX in decimal form which would be
rejected by this check. Instead of fixing this check just remove it.
Signed-off-by: Ha
Instead of manually handling the frees use devm. There was also a free
missing in the unregister call which is not needed with devm.
Signed-off-by: Hauke Mehrtens
---
drivers/usb/host/bcma-hcd.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/host/bcma
These patches are fixing minor bugs and are adding support for ARM
based Broadcom BCM47XX and BCM53XX SoCs.
Changes since:
v1:
* add patch "USB: bcma: fix error handling in bcma_hcd_create_pdev()"
* do not call bcma_core_disable(dev, 0) before enable.
Hauke Mehrtens (6):
USB: bcma: remove ch
On some boards a GPIO is needed to activate USB controller. Make it
possible to specify such a GPIO in device tree.
Signed-off-by: Felix Fietkau
Signed-off-by: Hauke Mehrtens
---
drivers/usb/host/bcma-hcd.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/us
The Broadcom ARM SoCs with this usb core need a different
initialization and they have a different core id. This patch adds
support for these USB 2.0 core.
Signed-off-by: Felix Fietkau
Signed-off-by: Hauke Mehrtens
---
drivers/usb/host/bcma-hcd.c | 70 +++
This patch makes bcma_hcd_create_pdev() not return NULL, but a prober
error code in case of an error.
Signed-off-by: Hauke Mehrtens
---
drivers/usb/host/bcma-hcd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/bcma-hcd.c b/drivers/usb/host/bcma-hcd.c
in
The constants for these numbers were added long time ago, use them.
Signed-off-by: Hauke Mehrtens
---
drivers/usb/host/bcma-hcd.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/host/bcma-hcd.c b/drivers/usb/host/bcma-hcd.c
index 976b4e1..b4ec4ec 100644
--- a/dr
On 2 June 2015 at 21:35, Hauke Mehrtens wrote:
> These patches are fixing minor bugs and are adding support for ARM
> based Broadcom BCM47XX and BCM53XX SoCs.
>
> Changes since:
> v1:
> * add patch "USB: bcma: fix error handling in bcma_hcd_create_pdev()"
> * do not call bcma_core_disable(dev, 0
Hi Colin,
Thank you for the patch.
On Tuesday 02 June 2015 19:05:13 Colin King wrote:
> From: Colin Ian King
>
> isp1760_ep_alloc_request allocates a structure with kzalloc without checking
> for NULL and then returns a pointer to one of the structure fields. As the
> field happens to be the fi
On Tue, Jun 02, 2015 at 06:16:20PM +0300, Alexander wrote:
> Hello. I have got "Asus Z87-Expert" motherboard with integrated bluetooth
> adapter. It causes the following error on boot:
> "usb 3-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409"
> Though there are no real problems w
37 matches
Mail list logo
