Hi Heiner,
On Jun 17 2016 or thereabouts, Heiner Kallweit wrote:
> This patch migrates the USB LED driver to the HID subsystem.
> Supported are Dream Cheeky Webmail Notifier / Friends Alert
> and Riso Kagaku Webmail Notifier.
>
> Benefits:
> - Avoid using USB low-level calls and use the HID
On Jun 17 2016 or thereabouts, Heiner Kallweit wrote:
> The USB LED driver exposes a undocumented sysfs interface and doesn't
> use the standard kernel LED subsystem. It supports three devices:
>
> Delcom Visual Signal Indicator
> The driver supports generation 1 of the device only which was
>
On 17/06/2016 at 13:44:22 +, Yang, Wenyou wrote :
> Hi Alexandre,
>
> > -Original Message-
> > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> > Sent: 2016年6月9日 4:38
> > To: Rob Herring
> > Cc: Yang, Wenyou ; Alan Stern
Hi Alexandre,
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> Sent: 2016年6月9日 4:38
> To: Rob Herring
> Cc: Yang, Wenyou ; Alan Stern
> ; Greg Kroah-Hartman
>
On Sunday 05 June 2016 08:29 PM, Hans de Goede wrote:
> The A31 companion pmic (axp221) does not generate vbus change interrupts
> when the board is driving vbus, so we must poll when using the pmic for
> vbus-det _and_ we're driving vbus.
>
> Signed-off-by: Hans de Goede
On Sunday 05 June 2016 08:29 PM, Hans de Goede wrote:
> Use the new of_usb_get_dr_mode_by_phy() function to get the dr_mode
> from the musb controller node instead of assuming that having an id_det
> gpio means otg mode, and not having one means host mode.
>
> Implement peripheral-only mode by
Hi Guenter,
On 2016/6/17 12:59, Guenter Roeck wrote:
On 06/16/2016 07:09 PM, Frank Wang wrote:
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required
Hi Roger,
Roger Quadros writes:
>> This series centralizes OTG/Dual-role functionality in the kernel.
>> As of now I've got Dual-role functionality working pretty reliably on
>> dra7-evm and am437x-gp-evm.
>
> Do you have any comments on this series? If yes I can include them
>
Hi all,
We have an well-known problem that the device needs to do some power
sequence before it can be recognized by related host, the typical
example like hard-wired mmc devices and usb devices. This power
sequence is hard to be described at device tree and handled by
related host driver, so we
Signed-off-by: Neil Armstrong
---
.../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 95 ++
1 file changed, 95 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
diff --git
The individual driver file name is better to contain module name.
Signed-off-by: Peter Chen
---
.../power/pwrseq/{pwrseq-simple.txt => mmc-pwrseq-simple.txt} | 0
drivers/power/pwrseq/Makefile | 4 ++--
From: Peter Chen
Since the hcd (chipidea core device) has no device node, so
if we want to describe the child node under the hcd, we had
to put it under its parent's node (glue layer device), and
in the code, we need to let the hcd knows glue layer's code,
then the USB
Add binding doc for generic usb power sequence driver, and update
generic usb device binding-doc accordingly.
Signed-off-by: Peter Chen
---
.../bindings/power/pwrseq/pwrseq-usb-generic.txt | 31 ++
.../devicetree/bindings/usb/usb-device.txt | 2
From: Krzysztof Kozlowski
The "mmc" prefix is no longer needed after moving the pwrseq core code
from mmc/ to power/.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
From: Krzysztof Kozlowski
Allow build testing for power sequence drivers.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
drivers/power/pwrseq/Kconfig | 4 ++--
1 file changed, 2
Some hard-wired USB devices need to do power sequence to let the
device work normally, the typical power sequence like: enable USB
PHY clock, toggle reset pin, etc. But current Linux USB driver
lacks of such code to do it, it may cause some hard-wired USB devices
works abnormal or can't be
Add driver for generic power sequence support for USB deivces
which handles below things:
- Clock and its frequencies
- GPIO for reset and the duration time
- GPIO for enable
- Regulator for power
Signed-off-by: Peter Chen
---
drivers/power/pwrseq/Kconfig | 11
From: Peter Chen
The current dts describes USB HUB's property at USB controller's
entry, it is improper. The USB HUB should be the child node
under USB controller, with "usb-pwrseq" phandle to handle power
sequence stuffs.
Signed-off-by: Peter Chen
From: Krzysztof Kozlowski
Before moving pwrseq drivers from drivers/mmc/core/ to drivers/power/,
they were maintained by Ulf Hansson.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
These helpers are only used by mmc now, change them as generic and
do corresponding changes at mmc code.
Meanwhile, change return value of helper pwrseq_pre_power_on since
it may occur error during enable clock/regulator, etc.
Signed-off-by: Peter Chen
---
From: Krzysztof Kozlowski
The MMC power sequence drivers are useful also outside of MMC world: for
USB devices needed a hard-reset before probing. Before extending and
re-using pwrseq drivers, move them to a new place.
The commit does not introduce significant changes
Dear Heiko,
On 06/17/2016 07:15 AM, Heiko Stübner wrote:
Hi William,
Am Donnerstag, 2. Juni 2016, 20:34:56 schrieb William Wu:
This patch adds the devicetree documentation required for Rockchip
USB3.0 core wrapper consisting of USB3.0 IP from Synopsys.
It supports DRD mode, and could operate
In order to support the Qualcomm MDM9615 in the Sierra Wireless WP8548
Modules, add the Qualcomm HSIC USB PHY used inside the MDM9615 SoC.
This patchset is part of a global SoC + Module + Board support for the
Sierra Wireless mangOH Board support with the WP8548 module.
Neil Armstrong (2):
Add support for the HSIC PHY present in the Qualcomm MSM9615 SoC.
This PHY is also present on other SoCs and would need some changes.
Signed-off-by: Neil Armstrong
---
drivers/usb/phy/Kconfig | 13 +
drivers/usb/phy/Makefile| 1 +
From: Krzysztof Kozlowski
The power sequence hooks (mmc_pwrseq_pre_power_on(),
mmc_pwrseq_post_power_on() and mmc_pwrseq_power_off()) can be made more
generic to allow re-use in other subsystems. They do not need to take
pointer to struct mmc_host but instead the struct
It will be crash to stop gadget when the dwc3 device had been into suspend
state, thus we need to check if the dwc3 device had been into suspend state
when UDC try to stop gadget.
By the way I have rebased on your 'testing/next' branch.
Signed-off-by: Baolin Wang
---
Alan, thank you for the analysis and you are correct in your
assumption that this is a plain dumb thumb drive. The puzzling thing
for me is that the drive only shows this bottleneck under Linux and
not under Max OS X or Windows. Here are my results for Linux vs. Mac
OS X again:
Write speed under
This patch migrates the USB LED driver to the HID subsystem.
Supported are Dream Cheeky Webmail Notifier / Friends Alert
and Riso Kagaku Webmail Notifier.
Benefits:
- Avoid using USB low-level calls and use the HID subsystem instead
(as this device provides a USB HID interface)
- Use standard
On Fri, 17 Jun 2016, Michael Schaller wrote:
> Alan, thank you for the analysis and you are correct in your
> assumption that this is a plain dumb thumb drive. The puzzling thing
> for me is that the drive only shows this bottleneck under Linux and
> not under Max OS X or Windows. Here are my
Add urb tracepoints for host mode.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_host.c | 34 ++-
drivers/usb/musb/musb_trace.h | 63 +++
2 files changed, 71 insertions(+), 26 deletions(-)
diff --git
Add usb_request tracepoints for gadget mode.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_gadget.c | 35 ---
drivers/usb/musb/musb_trace.h | 76 ++
2 files changed, 90 insertions(+), 21 deletions(-)
diff --git
Switch dev_dbg() to tracepoint debug musb_dbg().
Signed-off-by: Bin Liu
---
drivers/usb/musb/cppi_dma.c| 50 +
drivers/usb/musb/musb_core.c | 64 +++---
drivers/usb/musb/musb_cppi41.c | 12 ++---
drivers/usb/musb/musb_gadget.c
musb core already exports the register read/write wrappers, so clean up
the duplication in dsps glue.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_dsps.c | 112 +--
1 file changed, 44 insertions(+), 68 deletions(-)
diff --git
This adds tracepoints to musb register read/write wrappers to get
trace log for register access.
The default tacepoint log prefix here would be musb_readX/writeX(),
which is not much helpful. So this patch let the tracepoints use
__buildin_return_address(0) to print the caller funciton name to
davinci.h is not required by cppi_dma.h but cppi_dma.c, so move the
include to the right place.
Signed-off-by: Bin Liu
---
drivers/usb/musb/cppi_dma.c | 1 +
drivers/usb/musb/cppi_dma.h | 8
2 files changed, 1 insertion(+), 8 deletions(-)
diff --git
On Fri, Jun 17, 2016 at 11:46 AM, wrote:
>> -Original Message-
>> From: Andy Lutomirski [mailto:l...@amacapital.net]
>> Sent: Thursday, June 16, 2016 1:41 PM
>> To: Limonciello, Mario
>> Cc: Greg Kroah-Hartman
Move struct cppi41_dma_channel to the header file so other modules can
use it.
Signed-off-by: Bin Liu
---
drivers/usb/musb/cppi_dma.h| 23 ++-
drivers/usb/musb/musb_cppi41.c | 21 +
2 files changed, 23 insertions(+), 21 deletions(-)
This adds tracepoints to dump musb interrupt events.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_core.c | 4 +---
drivers/usb/musb/musb_trace.h | 21 +
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c
Hi Greg,
This musb patch set is for next v4.8. It adds tracepoints to musb drivers
to help debugging.
The patches have been on linux-usb@ list for a couple weeks now. Please
let me know if any change is needed.
Regards,
-Bin.
---
Bin Liu (10):
usb: musb: add tracepoints support for debugging
To avoid printk() overhead while debugging, this patch implements the
foundation of tracepoints logging for musb driver to make debug
easier.
Signed-off-by: Bin Liu
---
drivers/usb/musb/Makefile | 5 +++-
drivers/usb/musb/musb_debug.h | 2 ++
drivers/usb/musb/musb_trace.c |
On Fri, Jun 17, 2016 at 07:41:26PM +0200, Michael Schaller wrote:
> Alan, thank you for the analysis and you are correct in your
> assumption that this is a plain dumb thumb drive. The puzzling thing
> for me is that the drive only shows this bottleneck under Linux and
> not under Max OS X or
Greg, for my initial tests I did a sync afterwards and it finished
immediately on Linux and Mac OS X. Sorry for not mentioning that
earlier.
Furthermore 270 MB/s is the advertised write rate of the flash drive.
Mac OS X and Window can both write at the advertised speed and Linux
only reaches ~45
> -Original Message-
> From: Andy Lutomirski [mailto:l...@amacapital.net]
> Sent: Thursday, June 16, 2016 1:41 PM
> To: Limonciello, Mario
> Cc: Greg Kroah-Hartman ; Andy Lutomirski
> ; Mathias Nyman
On Fri, Jun 17, 2016 at 08:30:47PM +0200, Michael Schaller wrote:
> Greg, for my initial tests I did a sync afterwards and it finished
> immediately on Linux and Mac OS X. Sorry for not mentioning that
> earlier.
That's really odd, and is not normal for either OS.
> Furthermore 270 MB/s is the
Am 17.06.2016 um 10:53 schrieb Benjamin Tissoires:
> Hi Heiner,
>
> On Jun 17 2016 or thereabouts, Heiner Kallweit wrote:
>> This patch migrates the USB LED driver to the HID subsystem.
>> Supported are Dream Cheeky Webmail Notifier / Friends Alert
>> and Riso Kagaku Webmail Notifier.
>>
>>
In all cases the flash drive was completely zeroed out and hence there
was nothing to mount.
I'll have a look into fio once I have time again to play with this.
Might be 2-3 weeks though because of vacation...
On Fri, Jun 17, 2016 at 9:02 PM, Greg KH wrote:
> On Fri,
On Fri, 17 Jun 2016, Michael Schaller wrote:
> Alan, here is the requested information. Sorry for the delay.
>
> Started usbmon log with no connected USB devices:
> $ sudo cat /sys/kernel/debug/usb/usbmon/0u | tee usbmon.txt
> ...
>
> See the attached usbmon.txt.gz
Okay, it's got what we need.
Add tracepoints for cppi41 dma channels.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_cppi41.c | 22 ++---
drivers/usb/musb/musb_trace.h | 70 ++
2 files changed, 80 insertions(+), 12 deletions(-)
diff --git
On Fri, Jun 17, 2016 at 10:33:52PM +0200, Jiri Kosina wrote:
> On Fri, 17 Jun 2016, Heiner Kallweit wrote:
>
> > The USB LED driver exposes a undocumented sysfs interface and doesn't
> > use the standard kernel LED subsystem. It supports three devices:
> >
> > Delcom Visual Signal Indicator
> >
On Thu, Jun 16, 2016 at 08:27:41AM +0800, Lu Baolu wrote:
> Hi Greg,
>
> On 06/09/2016 10:39 AM, Lu Baolu wrote:
> > Hi Greg,
> >
> > On 06/08/2016 11:45 PM, Greg Kroah-Hartman wrote:
> >> On Wed, Jun 08, 2016 at 03:56:04PM +0800, Lu Baolu wrote:
> >>> Hi Greg,
> >>>
> >>> On 06/08/2016 12:45 PM,
On Fri, 17 Jun 2016, Heiner Kallweit wrote:
> This patch migrates the USB LED driver to the HID subsystem.
> Supported are Dream Cheeky Webmail Notifier / Friends Alert
> and Riso Kagaku Webmail Notifier.
I have dropped the mentions of this being specific to USB from the Kconfig
help text as
On Fri, 17 Jun 2016, Heiner Kallweit wrote:
> The USB LED driver exposes a undocumented sysfs interface and doesn't
> use the standard kernel LED subsystem. It supports three devices:
>
> Delcom Visual Signal Indicator
> The driver supports generation 1 of the device only which was
>
On Sun, Jun 12, 2016 at 06:47:56PM +0200, Marc Haber wrote:
> On Sat, Jun 11, 2016 at 02:55:04PM +0200, Marc Haber wrote:
> > On Tue, Jun 07, 2016 at 10:30:17AM -0700, Greg KH wrote:
> > > Nothing obvious, can you use 'git bisect' to go from 4.5.0 to 4.6.0 to
> > > find the offending commit?
> >
Hello everybody!
On Tue, 14 Jun 2016 13:41:07 -0700 Greg KH wrote:
> On Sun, Jun 12, 2016 at 10:40:55PM +0200, Lars Täuber wrote:
> > Hello kernel hackers,
> >
> > please excuse the way I'm writing this. I know I'm for sure braking rules.
> > I'm trying to use the
Hi Peter,
On 17.06.2016 12:09, Peter Chen wrote:
> Hi all,
>
> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices. This power
> sequence is hard to be
On Fri, Jun 17, 2016 at 5:09 AM, Peter Chen wrote:
> Add binding doc for generic usb power sequence driver, and update
> generic usb device binding-doc accordingly.
>
> Signed-off-by: Peter Chen
> ---
> .../bindings/power/pwrseq/pwrseq-usb-generic.txt |
Hi Greg,
On Fri, Jun 17, 2016 at 12:31:59PM -0500, Bin Liu wrote:
> Hi Greg,
>
> This musb patch set is for next v4.8. It adds tracepoints to musb drivers
> to help debugging.
>
> The patches have been on linux-usb@ list for a couple weeks now. Please
> let me know if any change is needed.
I
Hi,
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.7-rc3 next-20160617]
[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-ci/linux/commits/Neil-Armstrong/usb-phy-Add-support
Alan, here is the requested information. Sorry for the delay.
Started usbmon log with no connected USB devices:
$ sudo cat /sys/kernel/debug/usb/usbmon/0u | tee usbmon.txt
...
See the attached usbmon.txt.gz
Timing:
Connect of flash drive at: 16:09:04
dmesg output after connect of flash
On Fri, 17 Jun 2016, Peter Chen wrote:
> Some hard-wired USB devices need to do power sequence to let the
> device work normally, the typical power sequence like: enable USB
> PHY clock, toggle reset pin, etc. But current Linux USB driver
> lacks of such code to do it, it may cause some
Make at91_dt_syscon_sfr() static as it is not used or declared
outside the drivers/usb/host/ohci-at91.c file.
drivers/usb/host/ohci-at91.c:144:15: warning: symbol 'at91_dt_syscon_sfr' was
not declared. Should it be static?
Signed-off-by: Ben Dooks
---
Cc: Alan Stern
On 17/06/2016 at 16:11:55 +0100, Ben Dooks wrote :
> Make at91_dt_syscon_sfr() static as it is not used or declared
> outside the drivers/usb/host/ohci-at91.c file.
>
> drivers/usb/host/ohci-at91.c:144:15: warning: symbol 'at91_dt_syscon_sfr' was
> not declared. Should it be static?
>
>
Great tip, Alan. I'll look into capturing USB traffic with Wireshark
as well. Both fio and Wireshark should be available for Linux and
Windows.
On Fri, Jun 17, 2016 at 10:11 PM, Alan Stern wrote:
> On Fri, 17 Jun 2016, Michael Schaller wrote:
>
>> Alan, thank you for
Hi Kishon,
Am Freitag, 17. Juni 2016, 17:24:46 schrieb Kishon Vijay Abraham I:
> > + ret = of_clk_add_provider(node, of_clk_src_simple_get, rphy->clk480m);
> > + if (ret < 0)
> > + goto err_clk_provider;
> > +
> > + ret = devm_add_action(rphy->dev,
On 06/17/2016 03:25 AM, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 in the Sierra Wireless WP8548
> Modules, add the Qualcomm HSIC USB PHY used inside the MDM9615 SoC.
>
> This patchset is part of a global SoC + Module + Board support for the
> Sierra Wireless mangOH Board
Hi Felipe,
On 13 June 2016 at 23:13, Jun Li wrote:
> Hi
>
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Baolin Wang
>> Sent: Monday, June 13, 2016 4:47 PM
>> To: ba...@kernel.org;
The USB LED driver exposes a undocumented sysfs interface and doesn't
use the standard kernel LED subsystem. It supports three devices:
Delcom Visual Signal Indicator
The driver supports generation 1 of the device only which was
manufactured until 2008. Remove support for this device completely.
Am 16.06.2016 um 21:13 schrieb Greg Kroah-Hartman:
> On Thu, Jun 16, 2016 at 09:00:50PM +0200, Heiner Kallweit wrote:
>> The USB LED driver exposes a undocumented sysfs interface and doesn't
>> use the standard kernel LED subsystem. It supports three devices:
>>
>> Delcom Visual Signal Indicator
This patch migrates the USB LED driver to the HID subsystem.
Supported are Dream Cheeky Webmail Notifier / Friends Alert
and Riso Kagaku Webmail Notifier.
Benefits:
- Avoid using USB low-level calls and use the HID subsystem instead
(as this device provides a USB HID interface)
- Use standard
On 17/06/16 10:17, Felipe Balbi wrote:
>
> Hi Roger,
>
> Roger Quadros writes:
>>> This series centralizes OTG/Dual-role functionality in the kernel.
>>> As of now I've got Dual-role functionality working pretty reliably on
>>> dra7-evm and am437x-gp-evm.
>>
>> Do you have any
Hi,
On Monday 13 June 2016 07:40 AM, Frank Wang wrote:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank Wang
71 matches
Mail list logo