On Tue, Jul 08, 2014 at 09:58:39PM -0400, Nicholas Krause wrote:
> This patch removes a fixme message in this file:wq for setting the usb 2
:wq?
> speed on the board to the correct level. We need to depend on the
> bootloader for doing this as the wires may be shared for the other
> things on the
Hi,
On Tue, Jul 08, 2014 at 08:28:59PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 07/08/2014 02:14 PM, Markus Pargmann wrote:
>
> >fsl,usbphy is no optional property. This patch moves it to the list of
> >required properties.
>
> >Signed-off-by: Markus Pargmann
> >---
> > Documentation/dev
The maximum jumbo frame size for RTL8153 is 9K bytes.
Change the max rx packet size to 9K.
Change the use of the shared fifo from 6K (default) to 12K for tx.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 39 +++
1 file changed, 35 insertions(+), 4 de
From: loody
...
> but what it really do is read sector, not media_change or test_unit_ready.
Maybe one of the programs that reads the mbr partition table can
be persuaded to do a direct read?
David
On 07/08/2014 02:51 PM, Jingoo Han wrote:
> Use SIMPLE_DEV_PM_OPS macro and remove DEV_PM_OPS macro, in order
> to make the code simpler.
>
> Signed-off-by: Jingoo Han
Acked-by: Roger Quadros
> ---
> drivers/usb/phy/phy-am335x.c | 12 +++-
> 1 file changed, 3 insertions(+), 9 deleti
Hi,
On Mon, Jun 9, 2014 at 9:19 AM, Pratyush Anand wrote:
> On Fri, Jun 06, 2014 at 08:12:12PM +0800, Vivek Gautam wrote:
>> Some PHY controllers may need to calibrate certain
>> PHY settings after initialization of the controller and
>> sometimes even after initializing the PHY-consumer too.
>>
commit c63d2225e7be ("usb: gadget: pxa25x_udc: use devm_ functions")
introduced the use of devm_gpio_request in this driver, but did not
correctly include the header file declaring this function, which
causes a build failure.
This changes pxa25x_udc to include linux/gpio.h instead of asm/gpio.h
to
The host controller by itself may sometimes need to handle PHY
and/or calibrate some of the PHY settings to get full support out
of the PHY controller. The PHY core provides a calibration
funtionality now to do so.
Therefore, facilitate getting the two possible PHYs, viz.
USB 2.0 type (UTMI+) and U
Some quirky PHYs may require to be calibrated post the host
controller initialization.
The USB 3.0 DRD PHY on Exynos5420/5800 systems, coming along with
Synopsys's DWC3 controller, is one such PHY which needs to be
calibrated post xhci's reset at initialization time and at
resume time, to get the c
This series is based on Heikki's patches for simpliefied phy lookup table:
[PATCHv2 0/6] phy: simplified phy lookup [1], applied against 'next' branch
of Kishon's linux-phy tree.
Changes since v1:
1) Using 'gen_phy' member of 'hcd' instead of declaring more variables
to hold phys.
2) Added a ch
Adding phy calibrate callback, which facilitates setting certain
PHY settings post initialization of the PHY controller.
Exynos5420 and Exynos5800 have 28nm USB 3.0 DRD PHY for which
the Loss-of-Signal (LOS) Detector Threshold Level as well as
Tx-Vboost-Level should be controlled for Super-Speed op
Some PHY controllers may need to calibrate certain
PHY settings after initialization of the controller and
sometimes even after initializing the PHY-consumer too.
Add support for the same in order to let consumers do so in need.
Signed-off-by: vivek Gautam
---
drivers/phy/phy-core.c | 36
On Wed, Jul 9, 2014 at 2:08 AM, Kuninori Morimoto
wrote:
>
> Hi Ulrich
>
> Thank you for your patch
Thank you for your review.
>> @@ -186,6 +192,8 @@ struct renesas_usbhs_platform_info {
>>* driver use these param for some register
>>*/
>> struct renesas_usbhs_driver_param
Hi,
On Tuesday, July 08, 2014 08:04:47 PM Paul Zimmerman wrote:
> > From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> > Sent: Tuesday, July 08, 2014 7:55 AM
> >
> > The commit 5b7d70c6dbf2 ("USB: Gadget driver for Samsung HS/OtG
> > block") which added this driver also introduc
This patch adds the support to PHY framework in HCD code while keeping
the USB PHY compatibility. Changes are done in both the HCD common code
and in the drivers accessing its PHY. This is done in two steps:
renaming 'phy' into 'usb_phy' and adding a new 'phy' member into the
usb_hcd structure.
Si
OS String descriptor can be provided by using FunctionFS with configfs.
In order for FunctionFS to support Feature Descriptors, corresponding
Extended Compatibility and Extended Properties descriptors must be
passed to ep0. This series adds parsing the said descriptors and
setting up appropriate in
Provide helper functions to get pointers to particular locations within
a buffer holding an extended properties descriptor.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/usb/gadget/u_os_desc.h | 59 --
1 file changed, 46 insertions(+), 13 deletions(-)
ffs_do_desc() handles one descriptor, while ffs_do_descs() handles a number
of descriptors. The tho names are so similar that it causes confusion.
Rename to reflect their purpose better.
Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Michal Nazarewicz
---
drivers/usb/gadget/function/f_fs.c | 7
Add support for OS descriptors. The new format of descriptors is used,
because the "flags" field is required for extensions. os_count gives
the number of OSDesc[] elements.
The format of descriptors is given in include/uapi/linux/usb/functionfs.h.
For extended properties descriptor the usb_ext_pro
This patch adds the support to the PHY framework for ChipIdea drivers
while keeping the USB PHY compatibility. Changes are done in both the
ChipIdea common code and in the drivers accessing the PHY. This is done
by renaming 'phy' into 'usb_phy' and adding a new 'phy' member into the
ci_hdrc structr
Hi all,
This is an attempt to add more common USB code aware of the generic PHY
framework, while keeping the compatibility for the USB PHY one. It does
not add the full support, some USB PHY specific functions not being
available currently in the generic PHY subsystem (e.g. usb_phy_set_power()).
B
This patch adds the support to PHY framework in OTG code, and keeps the
USB PHY compatibility. This is done in two steps: renaming 'phy' into
'usb_phy' and adding a new 'phy' member into the usb_otg structure.
These modifications are done in all drivers accessing the OTG PHY.
Signed-off-by: Antoin
When gadgets are composed with configfs the user must know what are the
available function names. The names are parts of usb_f_*.ko
modules' aliases. If a function is compiled as a module, the information
can be found in modules.alias file. But if a function is compiled-in,
there is no way to know
Please disregard this patch.
It contains a bug: function names are copied to the destination buffer first,
and only after that the buffer overrun check is performed, which effectively
means that in the pessimistic scenario the buffer overflow happens first,
and then it is detected. Should be the
>From a5aea0fe3afcdfea82f08806856747e426ba8064 Mon Sep 17 00:00:00 2001
From: Yoshihiro Shimoda
Date: Wed, 9 Jul 2014 20:18:56 +0900
Subject: [PATCH 0/2] usb: renesas_usbhs: gadget: fix for g_zero
This patch fixes an issue that the renesas_usbhs driver in gadget mode
cannot work correctly even if
This patch fixes an issue that the renesas_usbhs driver in gadget mode
cannot work correctly even if I disabled DMAC of the driver when I used
the g_zero driver and the testusb tool.
When a usb cable is re-connected, the renesas_usbhs driver calls the
usbhsp_flags_init() (via usbhs_hotplug() --> u
This patch fixes an issue that the driver cannot push a new data when
a pipe is re-enabled after the pipe is queued.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/renesas_usbhs/pipe.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/renesas_usbhs/pipe.c b/drivers/usb/renesas
On 7 July 2014 17:08, Oleksij Rempel wrote:
> Am 07.07.2014 15:40, schrieb Anders Darander:
>> On 4 July 2014 18:54, Oleksij Rempel wrote:
>>> Am 04.07.2014 18:30, schrieb Alan Stern:
On Fri, 4 Jul 2014, Anders Darander wrote:
> ~# usb 1-1: new full-speed USB device number 3 using at91_o
* Roger Quadros [140630 04:02]:
> The ldousb_reg regulator provides power to the USB1 and USB2
> High Speed PHYs.
Applying this one into omap-for-v3.17/dt thanks.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
Mo
When gadgets are composed with configfs the user must know what are the
available function names. The names are parts of usb_f_*.ko
modules' aliases. If a function is compiled as a module, the information
can be found in modules.alias file. But if a function is compiled-in,
there is no way to know
Hello.
On 07/09/2014 05:58 AM, Nicholas Krause wrote:
This patch removes a fixme message in this file:wq for setting the usb 2
The vim's commands interspersed with text? :-)
speed on the board to the correct level. We need to depend on the
bootloader for doing this as the wires may be sh
On Mon, Jul 07, 2014 at 10:34:30PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jul 07, 2014 at 11:24:42AM +0200, Johan Hovold wrote:
> > I ended up getting the same laptop so now I'm facing the same problem
> > with repeated disconnects (especially during resume, which is really
> > annoying as it
The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
tags/usb-serial-3.16-rc5
for you to fetch changes up to 3d28bd8
hi all:
I try 2 methods today but there is no read command firing from usb
host to device
(I double check the existence of command by CATC protocol analyzer)
appreciate all your kind suggestion.
1. use busybox like below command
dd if=/dev/sda1 of=/dev/null bs=512 count=1 conv=sync
my dd in busybo
On Tue, 8 Jul 2014, Andrew Bresticker wrote:
> > I think at the very least you should add a function
> > "xhci_default_driver(struct hc_driver *driver)" to xhci-plat.c (or
> > even better to xhci.c and use it for PCI as well) that initializes all
> > function pointers to the default (internal) sym
Hello,
I have been using this particular device (on another machine with an older
kernel) for years without problems.
Unfortunately I ran into problems on my new machine with a 3.15.3 kernel now.
The device suddenly stopped working yesterday rendering the machine mostly
unusable and producing 18
hi Bryn:
2014-07-08 0:25 GMT+08:00 Bryn M. Reeves :
> On Tue, Jul 08, 2014 at 12:15:54AM +0800, loody wrote:
>> so sg_read will not hammer on the page cache like dd without "iflags=direct"
>>
>> thanks for your kind help,
>
> The sg_read program (and other programs in sg3_utils) sends a command di
On Wed, 9 Jul 2014, loody wrote:
> on that usb hard disk, no matter media_change or TEST_UNIT_READY, keep
> polling the device every 3mins.
> the disconnection still happen.
>
> So I am wondering, I can use the existence wheel, such as echo 4 >
> /sys/block/sda/events_poll_
> msecs.
> but wha
On Wed, 9 Jul 2014, loody wrote:
> hi all:
> I try 2 methods today but there is no read command firing from usb
> host to device
> (I double check the existence of command by CATC protocol analyzer)
> appreciate all your kind suggestion.
>
> 1. use busybox like below command
> dd if=/dev/sda1 of=
On Wed, 9 Jul 2014, Sven Geggus wrote:
> Hello,
>
> I have been using this particular device (on another machine with an older
> kernel) for years without problems.
>
> Unfortunately I ran into problems on my new machine with a 3.15.3 kernel now.
>
> The device suddenly stopped working yesterda
On Wed, 9 Jul 2014, Antoine Ténart wrote:
> This patch adds the support to PHY framework in HCD code while keeping
> the USB PHY compatibility. Changes are done in both the HCD common code
> and in the drivers accessing its PHY. This is done in two steps:
> renaming 'phy' into 'usb_phy' and adding
Alan Stern schrieb am Mittwoch, den 09. Juli um 16:26 Uhr:
> Those messages mean that the device crashed. It completely stopped
> sending USB packets. Unplugging it must have reset the device and
> caused it to start working again.
Hm. It definietely did not do this attached to the old machine
Hi Alan,
On Wed, Jul 09, 2014 at 10:41:50AM -0400, Alan Stern wrote:
> On Wed, 9 Jul 2014, Antoine Ténart wrote:
>
> > This patch adds the support to PHY framework in HCD code while keeping
> > the USB PHY compatibility. Changes are done in both the HCD common code
> > and in the drivers accessin
Introduce the module_usb_composite_driver macro as a convenience macro
for USB gadget composite driver modules, similar to module_usb_driver.
It is intended to be used by drivers which init/exit section does
nothing but calling usb_composite_probe/usb_composite_unrregister. By
using this macro it i
.
Patches are against linux-next 20140709.
Tobias Klauser (2):
usb: gadget: Add helper macro for usb_composite_driver boilerplate
usb: gadget: Convert drivers to use module_usb_composite_driver()
drivers/usb/gadget/acm_ms.c | 14 ++
drivers/usb/gadget/audio.c| 12
Use the module_usb_composite_driver() macro where applicable to
eliminate the module_init/module_exit boilerplate in USB gadget composite
drivers.
Signed-off-by: Tobias Klauser
---
drivers/usb/gadget/acm_ms.c | 14 ++
drivers/usb/gadget/audio.c | 12 +---
drivers/usb/gadget/
This patch removes a fixme message in this file for setting the usb 2
speed on the board to the correct level. We need to depend on the
bootloader for doing this as the wires may be shared for the other
things on the board with the usb chipset.
Signed-off-by: Nicholas Krause
---
arch/arm/mach-om
Ok, this has been fun to watch on lkml for a while now, but really,
please, just stop doing this. Randomly searching the kernel source for
FIXME lines and just commenting them out, isn't ok. Almost always,
those lines are there because the original developer really doesn't know
how else to resolv
On Wed, Jul 09, 2014 at 03:14:58PM +0200, Johan Hovold wrote:
> The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
>
> Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-
Greg KH wrote on July 9th at 1:19 P.M.
Ok, this has been fun to watch on lkml for a while now, but really,
please, just stop doing this. Randomly searching the kernel source for
FIXME lines and just commenting them out, isn't ok. Almost always,
those lines are there because the original developer
On Wed, Jul 9, 2014 at 3:01 AM, Vivek Gautam wrote:
> The host controller by itself may sometimes need to handle PHY
> and/or calibrate some of the PHY settings to get full support out
> of the PHY controller. The PHY core provides a calibration
> funtionality now to do so.
> Therefore, facilitate
On Wed, Jul 9, 2014 at 3:01 AM, Vivek Gautam wrote:
> Some quirky PHYs may require to be calibrated post the host
> controller initialization.
> The USB 3.0 DRD PHY on Exynos5420/5800 systems, coming along with
> Synopsys's DWC3 controller, is one such PHY which needs to be
> calibrated post xhci'
On Thu, May 29, 2014 at 10:03:42AM +0530, Pratyush Anand wrote:
> OTG3 and EH Compliance Plan 1.0 talks about Super Speed OTG Verification
> system (SS-OVS) which consists of an excersizer and analyzer.
>
> USB Compliance Suite from Lecroy or Ellisys can act as such SS-OVS for
> Link Layer Validat
On Mon, Jun 02, 2014 at 07:45:25PM +0200, Emil Goode wrote:
> The variable err is not initialized here, this patch uses it
> to store an eventual error value from devm_clk_get().
>
> Signed-off-by: Emil Goode
> Acked-by: Geert Uytterhoeven
> ---
> drivers/usb/misc/usb3503.c | 10 +++---
>
On Wed, Jul 02, 2014 at 01:58:18AM -0700, Chen, Alvin wrote:
> From: Bryan O'Donoghue
>
> The EHCI packet buffer in/out threshold is programmable for Intel Quark X1000
> USB host controller, and the default value is 0x20 dwords. The in/out
> threshold
> can be programmed to 0x80 dwords (512 Byte
On Sun, Jun 29, 2014 at 10:42:53PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Fix warning: drivers/usb/misc/usb3503.c:195:11: warning: 'err'
> may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> err is not initialized, the error return should be PTR_ERR(clk)
>
> Si
From: Hayes Wang
Date: Wed, 9 Jul 2014 16:07:02 +0800
> +static int rtl8152_change_mtu(struct net_device *dev, int new_mtu)
> +{
> + struct r8152 *tp = netdev_priv(dev);
> +
> + if (dev->mtu == new_mtu)
> + return 0;
This method will never be invoked if the MTU is actually no
Hi
> From a5aea0fe3afcdfea82f08806856747e426ba8064 Mon Sep 17 00:00:00 2001
> From: Yoshihiro Shimoda
> Date: Wed, 9 Jul 2014 20:18:56 +0900
> Subject: [PATCH 0/2] usb: renesas_usbhs: gadget: fix for g_zero
>
> This patch fixes an issue that the renesas_usbhs driver in gadget mode
> cannot work
Since the struct hc_driver is mostly the same across the xhci-pci,
xhci-plat, and the upcoming xhci-tegra driver, introduce the function
xhci_init_driver() which will populate the hc_driver with the default
xHCI operations. The caller must supply a setup function which will
be used as the hc_drive
It was suggested in the review of the Tegra xHCI driver [1] that we
allow xHCI drivers to be built as individual modules (like EHCI) instead
of building them all into the single xhci-hcd module as they are today.
Patches 1-3 prepare for making the xHCI PCI and platform drivers able
to be built as
In preparation for allowing the xHCI host controller drivers to be built
as separate modules, export symbols from the xHCI core that may be used
by the host controller drivers.
Signed-off-by: Andrew Bresticker
---
drivers/usb/host/xhci-dbg.c | 1 +
drivers/usb/host/xhci.c | 3 +++
2 files ch
Instead of calling xhci_compliance_mode_recovery_timer_quirk_check() again
in the PCI suspend path, just check for XHCI_COMP_MODE_QUIRK which will
have been set based on xhci_compliance_mode_recovery_timer_quirk_check()
in xhci_init().
Signed-off-by: Andrew Bresticker
---
drivers/usb/host/xhci-p
Instead of building all of the xHCI code into a single module, separate
it out into the core (xhci-hcd), PCI (xhci-pci, now selected by the new
config option CONFIG_USB_XHCI_PCI), and platform (xhci-plat) drivers.
Also update the PCI/platform drivers with module descriptions/licenses
and have them
This patch adds a firmware for the USB 3.0 host controller of Renesas
R-Car H2 and M2 SoCs.
Signed-off-by: Yoshihiro Shimoda
---
The xhci-rcar driver was merged in Greg usb.git / usb-next branch:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=4ac8918f3a737c21
The smsc95xx needs to resume with reset operation. Otherwise it causes
system hang by network error like below after resume. This case appears
on odroid u3 board.
[9.727600] smsc95xx 1-2:1.0 eth0: kevent 2 may have been dropped
[9.727648] smsc95xx 1-2:1.0 eth0: kevent 2 may have been dropp
The maximum jumbo frame size for RTL8153 is 9K bytes.
Change the max rx packet size to 9K.
Change the use of the shared fifo from 6K (default) to 12K for tx.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 36
1 file changed, 32 insertions(+), 4 delet
This fixes below build warning.
drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
dev_err(dev, "unable to request refclk (%d)\n", err);
^
Signed-off-by: Joony
Hello,
This patchset is simple just to fix and support PM for usb3503. They was
tested on odroid U3 board.
Thanks.
Joonyoung Shim (3):
usb: usb3503: fix build warning
usb: usb3503: add PM functions
USB: add reset resume quirk for usb3503
drivers/usb/core/quirks.c | 3 +++
d
The usb device will autoresume from choose_wakeup() if it is
autosuspended with the wrong wakeup setting, but below errors occur
because usb3503 misc driver will switch to standby mode when suspended.
As add USB_QUIRK_RESET_RESUME, it can stop setting wrong wakeup from
autosuspend_check().
[7
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2 deletions(-
Hi Joonyoung,
On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim wrote:
> This fixes below build warning.
>
> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
> drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ may be used uninitialized
> in this function [-Wmaybe-uninitialized]
> dev_e
On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
> Hi Joonyoung,
>
> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim
> wrote:
> > This fixes below build warning.
> >
> > drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
> > drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ ma
On 07/10/2014 02:05 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
>> Hi Joonyoung,
>>
>> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim
>> wrote:
>>> This fixes below build warning.
>>>
>>> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
>
The usb3503 needs to switch to standby mode while suspending and should
switch to hub mode when resumed. Also we can control clock on PM
function.
Signed-off-by: Joonyoung Shim
---
drivers/usb/misc/usb3503.c | 34 --
1 file changed, 32 insertions(+), 2 deletions(-
The usb device will autoresume from choose_wakeup() if it is
autosuspended with the wrong wakeup setting, but below errors occur
because usb3503 misc driver will switch to standby mode when suspended.
As add USB_QUIRK_RESET_RESUME, it can stop setting wrong wakeup from
autosuspend_check().
[7
75 matches
Mail list logo
