> Hi Peter,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on peter.chen-usb/ci-for-usb-next] [also build test
> ERROR
> on v4.19-rc8 next-20181012] [if your patch is applied to the wrong git tree,
> please
> drop us a note to help improve the system]
>
> url:
>
Hi Peter,
I love your patch! Yet something to improve:
[auto build test ERROR on peter.chen-usb/ci-for-usb-next]
[also build test ERROR on v4.19-rc8 next-20181012]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
For USB HSIC, the data and strobe pin needs to be pulled down
at default, we consider it as "idle" state. When the USB host
is ready to be used, the strobe pin needs to be pulled up,
we consider it as "active" state.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb
The chipidea controller has some special requirements during
suspend/resume, override common ehci->hub_control to implement
it.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/host.c | 74 +
1 file changed, 74 insertions(+)
diff --git a/drivers/usb
To support imx HSIC, there are some special requirement:
- The HSIC pad is 1.2v, it may need to supply from external
- The data/strobe pin needs to be pulled down first, and after
host mode is initialized, the strobe pin needs to be pulled up
- During the USB suspend/resume, special setting is ne
NXP (Freecale) imx HSIC design has some special requirements, add
some flags at host code to handle them.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/host.c | 24
include/linux/usb/chipidea.h | 3 +++
2 files changed, 27 insertions(+)
diff --git a/drivers/usb/c
Most of NXP (Freescale) i.mx USB part has HSIC support, in this series,
we add support for them, it should cover all imx6 and imx7d. I have
no HSIC interface board which is supported by upstream kernel, so this
patches are only compiled ok, Frieder Schrempf, would you please
help me test it on your
It is introduced for the pre-0.96 xHC controllers, and the driver only
support HW LPM for 1.0 and later controllers.It's not actually used now
and is thought not to be used in the future any more, so just remove it.
Acked-by: Mathias Nyman
Signed-off-by: Zeng Tao
---
drivers/usb/host/xhci-mem.c
Hi Mathias:
>-Original Message-
>From: Mathias Nyman [mailto:mathias.ny...@intel.com]
>Sent: Monday, October 15, 2018 8:11 PM
>To: Zengtao (B) ; Greg KH
>
>Cc: linux-ker...@vger.kernel.org; linux-usb@vger.kernel.org
>Subject: Re: Can we just remove the sw_lpm_support from current xhci
>dri
Did you get my email from last week?
Let me know if you have photos for cutting out or retouching?
We are an image team who can do editing for your the web store photos,
industry photos or portrait photos.
Send photos, we will do testing for you to check quality.
Waiting for your reply soon.
Th
The at91sam9rl PMC is not quite the same as the at91sam9g45 one and now has
its own compatible string. Add support for that.
Fixes: 217bace8e548 ("ARM: dts: fix PMC compatible")
Signed-off-by: Alexandre Belloni
Acked-by: Cristian Birsan
---
Hello Greg,
This is an urgent fix that was sent on s
Commit 7a68d9fb8510 ("USB: usbdevfs: sanitize flags more") checks the
transfer flags for URBs submitted from userspace via usbfs. However,
the check for whether the USBDEVFS_URB_SHORT_NOT_OK flag should be
allowed for a control transfer was added in the wrong place, before
the code has properly de
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+24a30223a4b609bb8...@syzkaller.appspotmail.com
Tested on:
commit: f0a7d1883d9f afs: Fix clearance of reply
git tree: upstream
kernel config: https://syzkall
On Wed, Sep 26, 2018 at 06:20:10PM -0400, Al Cooper wrote:
> Add DT bindings document for Broadcom STB USB OHCI, EHCI and
> XHCI drivers.
>
> Signed-off-by: Al Cooper
> ---
> .../devicetree/bindings/usb/brcm,ehci-brcm.txt | 22 +
> .../devicetree/bindings/usb/brcm,ohci-br
On Mon, Oct 15, 2018 at 7:12 PM, Alan Stern wrote:
> Ah, I see the problem. In fact it is the same issue, but the commit
> mentioned above contains an error (is_in gets tested too soon). The
> fix is below; can you check it?
You can ask syzbot to do this:
#syz test: git://git.kernel.org/pub/sc
On Mon, 15 Oct 2018, Andrey Konovalov wrote:
> On Mon, Oct 15, 2018 at 5:22 PM, Alan Stern wrote:
> > On Fri, 12 Oct 2018, syzbot wrote:
> >
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:9dcd936c5312 Merge tag 'for-4.19/dm-fixes-4' of
> >> git://git...
> >>
Hi Felipe,
I am having some issues when attempting to stream 1280x720 uncompressed video @
10fps over a USB 2.0 High-Speed link.
The system setup is:
WebCam --- USB 2.0 link ---> x86 Linux Machine running uvc-gadget USB 2.0
link ---> x86 Host Machine running Windows 10.
When run
On 10/13/2018 11:37 AM, Randy Dunlap wrote:
> Kernel 4.19-rc7, on x86_64:
>
> Load usbip_vudc module, then unload (rmmod) it.
> Load it again:
>
Thanks Randy. I am debugging another problem in this path and I will
take a look at this one as well. Just quick ack that I saw this.
Thanks for repor
On Mon, Oct 15, 2018 at 5:22 PM, Alan Stern wrote:
> On Fri, 12 Oct 2018, syzbot wrote:
>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:9dcd936c5312 Merge tag 'for-4.19/dm-fixes-4' of git://git...
>> git tree: upstream
>> console output: https://syzkaller.appspot
On Mon, 15 Oct 2018 tudor.amba...@microchip.com wrote:
> atmel,oc-gpio is optional. Request its irq only when atmel,oc is set
> in device tree.
>
> devm_gpiod_get_index_optional returns NULL if -ENOENT. Check its
> return value for NULL before error, because it is more probable that
> atmel,oc is
On Fri, 12 Oct 2018, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:9dcd936c5312 Merge tag 'for-4.19/dm-fixes-4' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=123b8da140
> kernel config: https://sy
Turned from arch/arm/mach-mmp/devices.c into a proper PHY driver, so
that in can be instantiated from a DT.
Acked-by: Kishon Vijay Abraham I
Signed-off-by: Lubomir Rintel
---
Greg,
please include this in the USB tree. Changes to mv-ehci driver that are already
in can utilize this and it got an
In FFS the support for multiple alternate interface settings are not present.
This patch implements the due support. The user application is required to
write interface descriptors to ep0 file of function fs, one for each alternate
interface setting of the same interface, with bAlternateSetting set
On Mon, 15 Oct 2018, Oliver Neukum wrote:
> On Do, 2018-10-11 at 14:29 -0400, Alan Stern wrote:
> > On Thu, 11 Oct 2018, Mayuresh Kulkarni wrote:
> [..]
> > > We are looking into closing the device instance during normal operation
> > > i.e.: only open/close device when needed.
> > >
> > > Howev
Ben Dooks writes:
> Add a configuration option for the default state of turbo mode
> on the smsc95xx networking driver. Some systems it is better
> to default this to off as it causes significant increases in
> soft-irq load.
So there is already a module option allowing you to change this, usin
Hi Oliver,
I'm currently using the latest 4.18.12 mainline ( on Arch
https://www.archlinux.org/packages/core/x86_64/linux/ ), and yes
you're right I am NOT using UAS at the moment. The link I left is
because I noticed those errors on dmesg, and I thought I had it
enabled. This is why I am writing
On 15.10.2018 12:35, Zengtao (B) wrote:
Hi:
I am recently reading the LPM related code in xhci driver, and I find
that the xhci->sw_lpm_support is not really used, but I am not sure
whether we should remove it or not?
Any ideas, Thanks.
I think it was used to prevent LPM in pre-0.96 xHC con
On So, 2018-10-14 at 13:40 +0200, Julian Xhokaxhiu wrote:
> Dear USB Driver module maintainers,
Hi,
thank you for the report
> Although sometimes, the system "hangs" very rarely, but in an annoying
> fashion that makes a bit sluggish the experience, which translates to
> weird dmesg errors like
On 12.10.2018 03:19, Peter Chen wrote:
Thanks, I should do it earlier, I could not find a suitable board with HSIC
support
at mainline kernel.
It is very kind that you could help on it and test function at real
board. My suggestion is follow all flows in Link [2] since we need to cover
sus
Hi:
I am recently reading the LPM related code in xhci driver, and I find
that the xhci->sw_lpm_support is not really used, but I am not sure
whether we should remove it or not?
Any ideas, Thanks.
Regards
Zengtao
On 15/10/2018 at 11:00, Tudor Ambarus - M18064 wrote:
atmel,oc-gpio is optional. Request its irq only when atmel,oc is set
in device tree.
devm_gpiod_get_index_optional returns NULL if -ENOENT. Check its
return value for NULL before error, because it is more probable that
atmel,oc is not set.
T
On Do, 2018-10-11 at 14:29 -0400, Alan Stern wrote:
> On Thu, 11 Oct 2018, Mayuresh Kulkarni wrote:
[..]
> > We are looking into closing the device instance during normal operation
> > i.e.: only open/close device when needed.
> >
> > However, we still have one particular use-case where our USB d
atmel,oc-gpio is optional. Request its irq only when atmel,oc is set
in device tree.
devm_gpiod_get_index_optional returns NULL if -ENOENT. Check its
return value for NULL before error, because it is more probable that
atmel,oc is not set.
This fixes the following errors on boards where atmel,oc
On 15/10/2018 at 10:34, Tudor Ambarus - M18064 wrote:
atmel,oc-gpio is optional. Request it's irq only when atmel,oc is set
in device tree.
devm_gpiod_get_index_optional returns NULL if -ENOENT. Check its
return value for NULL before error, because it is more probably that
atmel,oc is not set.
atmel,oc-gpio is optional. Request it's irq only when atmel,oc is set
in device tree.
devm_gpiod_get_index_optional returns NULL if -ENOENT. Check its
return value for NULL before error, because it is more probably that
atmel,oc is not set.
This fixes the following errors on boards where atmel,oc
35 matches
Mail list logo
