Hi,
On 10/24/2017 3:27 AM, Martin Blumenstingl wrote:
> This integrates the PHY roothub wrapper into the core hcd
> infrastructure. Multiple PHYs which are part of the roothub devicetree
> node (which is a sub-node of the sysdev's node) are now managed
> (= powered on/off when needed), by the
Hi,
On 10/26/2017 3:31 AM, Alex Elder wrote:
> No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support
> any more, so remove the code.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Alex Elder
> Acked-by: Bjorn Andersson
Hi,
On 10/26/2017 3:31 AM, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Alex Elder
> Acked-by: Bjorn Andersson
> Acked-by: Andy
From: "yinbo.zhu"
Add USB support on ls1088ardb
Signed-off-by: yinbo.zhu
Signed-off-by: Ran Wang
---
Change in v4:
- Change status from "enable" to "disabled" then enable it on
dts file.
- Add the
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/wusbcore/wa-xfer.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/wusbcore/wa-xfer.c
Hi,
On Wed, Oct 25, 2017 at 2:08 PM, Douglas Anderson wrote:
> On rk3288-veyron devices on Chrome OS it was found that plugging in an
> Arduino-based USB device could cause the system to lockup, especially
> if the CPU Frequency was at one of the slower operating points
No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
Suggested-by: Stephen Boyd
Signed-off-by: Alex Elder
Acked-by: Bjorn Andersson
Acked-by: Andy Gross
---
drivers/usb/host/Makefile
This series deletes some Qualcomm USB code is no longer needed by
any Qualcomm hardware.
-Alex
Alex Elder (3):
usb: host: remove ehci-msm.c
usb: phy: remove phy-msm-usb.c
usb: phy: remove phy-qcom-8x16-usb.c
drivers/usb/host/Makefile |
No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver
support any more, so remove the code.
Suggested-by: Stephen Boyd
Signed-off-by: Alex Elder
Acked-by: Bjorn Andersson
Acked-by: Andy Gross
No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support
any more, so remove the code.
Suggested-by: Stephen Boyd
Signed-off-by: Alex Elder
Acked-by: Bjorn Andersson
Acked-by: Andy Gross
---
Hi,
On Mon, Oct 16, 2017 at 1:49 PM, Julius Werner wrote:
>> d9a14b00 339317035 C Ii:1:004:1 -32:1 0
>> d9a14b00 339317049 S Ii:1:004:1 -115:1 10 <
>> d9a14b00 339318040 C Ii:1:004:1 -32:1 0
>> d9a14b00 339318057 S Ii:1:004:1 -115:1 10 <
>> d9a14b00 339319042 C Ii:1:004:1
On rk3288-veyron devices on Chrome OS it was found that plugging in an
Arduino-based USB device could cause the system to lockup, especially
if the CPU Frequency was at one of the slower operating points (like
100 MHz / 200 MHz).
Upon tracing, I found that the following was happening:
* The USB
Gal Shalif writes:
> Bjoren> You can always unbind the driver, right? And usb_modeswitch will
> even do it for you.
> I'm not a USB mode switch expert, so please explain what is the mode switch
> file that you suggest.
>
> As I already said before - my kernel configuration will
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/ehci-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/fotg210-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, this patchset aims
to mark switch cases where we are expecting to fall through.
In Kees Cook words:
"This is an unfortunate omission in the C language, and thankfully both
gcc and clang have stepped up to solve this the same way static
analyzers
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/ohci-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/xhci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/xhci.c
Greg,
Quoting "Gustavo A. R. Silva" :
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/isp1362-hcd.c | 1 +
1 file changed, 1
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/xhci-hub.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/xhci-hub.c
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/pci-quirks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/isp1362-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/isp1362-hcd.c
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/oxu210hp-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/xhci-mem.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/xhci-mem.c
This patch fix the following build warning:
drivers/usb/host/xhci-ring.c:1895:19: warning: variable 'urb_priv' set but not
used [-Wunused-but-set-variable]
Signed-off-by: Corentin Labbe
---
drivers/usb/host/xhci-ring.c | 2 --
1 file changed, 2 deletions(-)
diff --git
This patch fix the following build warning:
drivers/usb/host/xhci.c:2853:23: warning: variable 'ep' set but not used
[-Wunused-but-set-variable]
Signed-off-by: Corentin Labbe
---
drivers/usb/host/xhci.c | 2 --
1 file changed, 2 deletions(-)
diff --git
This patch fix the following build warnings:
drivers/usb/host/xhci.c:3378:6: warning: variable 'last_freed_endpoint' set but
not used [-Wunused-but-set-variable]
Signed-off-by: Corentin Labbe
---
drivers/usb/host/xhci.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
This patch fix the following build warnings:
drivers/usb/host/xhci-ring.c:2011:20: warning: variable 'ep_ring' set but not
used [-Wunused-but-set-variable]
Signed-off-by: Corentin Labbe
---
drivers/usb/host/xhci-ring.c | 2 --
1 file changed, 2 deletions(-)
diff --git
Oliver Neukum writes:
> Am Dienstag, den 24.10.2017, 23:17 +0300 schrieb Gal Shalif:
>> The option driver is compiled as a module.
>> The option driver patch, and other related patches are listed within
>> my previous email:
>
> Hi,
>
> but you are adding the device
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/udc/dummy_hcd.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/composite.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
-timer_setup/20171025-230118
config: i386-randconfig-x008-201743 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
In file included from i
-timer_setup/20171025-230118
config: x86_64-randconfig-x011-201743 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
In file included from i
On Wed, 25 Oct 2017, Felipe Balbi wrote:
> Hi,
>
> The following series was compile-tested only (so far, at least). I
> wanted to get some comments from folks to see what you guys think
> about this before running tests.
>
> I don't have any device available which would support PTM_STATUS so I
Commit 8b52291a0743 ("usb-storage: fix deadlock involving host lock
and scsi_done") added a local variable to usb_stor_control_thread() in
the usb-storage driver. This local variable holds the value of
us->srb, for use after the host lock has been released.
But as long as we have the value in a
On Tue, 24 Oct 2017, Uwe [iso-8859-1] Kleine-K�nig wrote:
> Now after removing my instrumentation the situation isn't what I
> described before. Instead of being spammed by messages about
> over-current I get only a single message (good) and power stays on. I
> wonder if that is acceptable.
>
>
This also uses timer_setup_on_stack() (only in -next). If it's okay,
I'll carry it in the timers tree.
Thanks!
-Kees
On Tue, Oct 24, 2017 at 12:08 PM, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks,
Sorry, I sent this one but forgot that timer_setup_on_stack() is in
-next only. If it's okay, I can carry it in the timers tree.
Thanks!
-Kees
On Tue, Oct 24, 2017 at 12:27 PM, Felipe Balbi
wrote:
> Kees Cook writes:
>
>> In preparation for
Hi,
Kishon Vijay Abraham I writes:
> Felipe,
>
> On Monday 09 October 2017 05:30 PM, Andrzej Pietrasiewicz wrote:
>> From: Vivek Gautam
>>
>> Adding phy calibration sequence for USB 3.0 DRD PHY present on
>> Exynos5420/5800 systems.
>> This calibration
Felipe,
On Monday 09 October 2017 05:30 PM, Andrzej Pietrasiewicz wrote:
> From: Vivek Gautam
>
> Adding phy calibration sequence for USB 3.0 DRD PHY present on
> Exynos5420/5800 systems.
> This calibration facilitates setting certain PHY parameters viz.
> the
USB 3.1 added a PTM_STATUS type. Let's add a define for it and
following patches will let usb_get_status() accept the new argument.
Signed-off-by: Felipe Balbi
---
drivers/usb/core/message.c | 4 ++--
include/uapi/linux/usb/ch9.h | 4
2 files changed, 6
Hi,
The following series was compile-tested only (so far, at least). I
wanted to get some comments from folks to see what you guys think
about this before running tests.
I don't have any device available which would support PTM_STATUS so I
guess I'd have to implement it on g_zero, if at all
This new 'type' parameter will allows interested drivers to request
for PTM status or Standard status.
Signed-off-by: Felipe Balbi
---
drivers/staging/wlan-ng/hfa384x_usb.c | 8 +++---
drivers/usb/core/driver.c | 3 ++-
drivers/usb/core/hub.c
This makes it a lot clearer that we're expecting a recipient as the
argument. A follow-up patch will use the argument 'type' as the status
type selector (standard or ptm).
Signed-off-by: Felipe Balbi
---
drivers/usb/core/message.c | 6 +++---
include/linux/usb.h
Now that we have more than one USB Status Type, we can provide helpers
to the users so that we reduce the amount of arguments that need to be
passed. This will also reduce the amount of mistakes when using this
API.
Signed-off-by: Felipe Balbi
---
On Wed, Oct 25, 2017 at 12:25:36PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> "Gustavo A. R. Silva" writes:
> > In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> > where we are expecting to fall through.
> >
> > Addresses-Coverity-ID: 115004
> >
Hi,
"Gustavo A. R. Silva" writes:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 115004
> Addresses-Coverity-ID: 115005
> Signed-off-by: Gustavo A. R. Silva
I have a donation gift for you. Reply asap
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Dienstag, den 24.10.2017, 23:17 +0300 schrieb Gal Shalif:
> The option driver is compiled as a module.
> The option driver patch, and other related patches are listed within
> my previous email:
Hi,
but you are adding the device unconditionally to the HID blacklist.
Thus the HID part becomes
On Oct 24 2017 or thereabouts, Allen Pais wrote:
> Switch to using the new timer_setup() and from_timer()
> for drivers/hid/*
>
> Cc: Kees Cook
> Signed-off-by: Allen Pais
> ---
>
> Note:This patch is only compile tested.
Looks good enough for me:
50 matches
Mail list logo