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 necessarily.
Signed-off-by: Frank Wang
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
Suggested-by: Guenter Roeck
Signed-off-by: Frank Wang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v6:
- Changed '_' to '-' for otg-id and otg-bvalid property.
Changes in v5:
- Added 'reg' property to identify the different phy-blocks.
The newer SoCs (rk3366, rk3399) of Rock-chip 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.
These series patches add phy-rockchip-inno-usb2.c and the corresponding
On Thu, Jun 16, 2016 at 02:02:37PM +0100, Ben Dooks wrote:
> On 14/06/16 12:08, Arnd Bergmann wrote:
> > On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
> drivers/usb/core/of.c:32:21: error: redefinition of
> 'usb_of_get_child_node'
> >> struct device_node
Hi Guenter,
On 2016/6/16 21:12, Guenter Roeck wrote:
On 06/15/2016 06:47 PM, Frank Wang wrote:
Hi Guenter & Heiko,
On 2016/6/15 23:47, Guenter Roeck wrote:
On Tue, Jun 14, 2016 at 6:14 PM, Frank Wang
wrote:
Hi Heiko & Guenter,
On 2016/6/14 22:00, Heiko Stübner
From: Hayes Wang
Date: Thu, 16 Jun 2016 14:08:29 +0800
> In set_speed(), BMCR_RESET would be set when the flag of PHY_RESET
> is set. Use BMCR_RESET to replace testing the flag of PHY_RESET.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
--
To
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 device mode (SS, HS, FS)
> and host mode (SS, HS,
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
> The driver supports generation 1 of the device only
Am 16.06.2016 um 09:08 schrieb Greg Kroah-Hartman:
> On Thu, Jun 16, 2016 at 07:45:35AM +0200, Heiner Kallweit wrote:
>> Am 15.06.2016 um 22:59 schrieb Heiner Kallweit:
>>> Am 15.06.2016 um 09:31 schrieb Benjamin Tissoires:
On Jun 15 2016 or thereabouts, Heiner Kallweit wrote:
> Am
On Sun, Mar 13, 2016 at 7:29 PM, Mario Limonciello
wrote:
>
>
> On 03/12/2016 02:33 PM, Andy Lutomirski wrote:
>> On Sat, Mar 12, 2016 at 11:35 AM, Andy Lutomirski
>> wrote:
>> Got it. I was barking up the wrong tree.
>>
>> Q: What happens if
Arnd Bergmann writes:
> We get a warning for this when building with W=1 because the
> argument gets assigned to something else but never read:
>
> drivers/usb/gadget/udc/pxa27x_udc.c: In function 'stop_activity':
> drivers/usb/gadget/udc/pxa27x_udc.c:1828:74: error: parameter
Hello Mathias,
On Thu, Jun 16, 2016 at 01:26:25PM +0300, Mathias Nyman wrote:
> This should be fixed with patch:
>
> commit 27a41a83ec54d0edfcaf079310244e7f013a7701
> xhci: Cleanup only when releasing primary hcd
>
> which is only in Gregs usb-linus branch, but should end up in Linus tree
On Thu, 16 Jun 2016, Sedat Dilek wrote:
> > sudo ./usbreset /dev/bus/usb/001/005
> >
> > 001 and 005 are the Bus and Device numbers from the lsusb output.
> >
>
> Thanks, Alan.
>
> I will look and test this (or adapt your) line as soon as I get in
> front of my machine.
>
> I have seen that
On 06/15/2016 06:47 PM, Frank Wang wrote:
Hi Guenter & Heiko,
On 2016/6/15 23:47, Guenter Roeck wrote:
On Tue, Jun 14, 2016 at 6:14 PM, Frank Wang wrote:
Hi Heiko & Guenter,
On 2016/6/14 22:00, Heiko Stübner wrote:
Am Dienstag, 14. Juni 2016, 06:50:31 schrieb
On 14/06/16 12:08, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
drivers/usb/core/of.c:32:21: error: redefinition of 'usb_of_get_child_node'
>> struct device_node *usb_of_get_child_node(struct device_node *parent,
>>
On 15/06/16 03:43, Peter Chen wrote:
> On Tue, Jun 14, 2016 at 01:08:08PM +0200, Arnd Bergmann wrote:
>> On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
> drivers/usb/core/of.c:32:21: error: redefinition of
> 'usb_of_get_child_node'
>>> struct device_node
We get a warning for this when building with W=1 because the
argument gets assigned to something else but never read:
drivers/usb/gadget/udc/pxa27x_udc.c: In function 'stop_activity':
drivers/usb/gadget/udc/pxa27x_udc.c:1828:74: error: parameter 'driver' set but
not used
I did some test-builds with W=1 and the -Wunused-but-set-variable
warnings appeared to be all fairly easy to address. In tons of
randconfig builds, I only found five instances.
The warning was originally disabled by Dave Jones when we hit
more instances with gcc-4.6, but apparently most of those
Hi Felipe,
On 10/06/16 16:07, Roger Quadros wrote:
> Hi,
>
> 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
On Wed, 15 Jun 2016, Andrew F. Davis wrote:
> On 06/15/2016 10:43 AM, Lee Jones wrote:
> > This requires a USB Ack.
> >
> >> The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter.
> >> Add MFD core support.
> >>
> >> Signed-off-by: Andrew F. Davis
> >> ---
> >
> > Where is the
On Thu, Jun 16, 2016 at 12:16 PM, Bjørn Mork wrote:
> Sedat Dilek writes:
>> On Wed, Jun 15, 2016 at 5:51 PM, Alan Stern
>> wrote:
>>
>>> sudo ./usbreset /dev/bus/usb/001/005
>>>
>>> 001 and 005 are the Bus and Device numbers
Sedat Dilek writes:
> On Wed, Jun 15, 2016 at 5:51 PM, Alan Stern wrote:
>
>> sudo ./usbreset /dev/bus/usb/001/005
>>
>> 001 and 005 are the Bus and Device numbers from the lsusb output.
>>
>
> Thanks, Alan.
>
> I will look and test this (or
On Wed, Jun 15, 2016 at 5:51 PM, Alan Stern wrote:
> On Wed, 15 Jun 2016, Sedat Dilek wrote:
>
>> Hi Alan,
>>
>> I updated my usb-ids on my Ubuntu 12.04 LTS (AMD64).
>> Background was my ASMedia ASM-104x USB-3.0 controller/hub shows no
>> human-readable vendor-string
Am Montag, den 06.06.2016, 16:56 +0100 schrieb Lee Jones:
> On the STiH410 B2120 development board the MiPHY28lp shares its reset
> line with the Synopsys DWC3 SuperSpeed (SS) USB 3.0 Dual-Role-Device
> (DRD). New functionality in the reset subsystems forces consumers to
> be explicit when
Hi Lee,
Am Dienstag, den 07.06.2016, 10:24 +0100 schrieb Lee Jones:
[...]
> I guess it should really go into the -rcs, yes. Since Hans' patch
> actually breaks a lot of devices. I'm pretty surprised a patch
> capable of this much damage was actually accepted to be honest.
I wasn't aware there
On Thu, Jun 16, 2016 at 07:45:35AM +0200, Heiner Kallweit wrote:
> Am 15.06.2016 um 22:59 schrieb Heiner Kallweit:
> > Am 15.06.2016 um 09:31 schrieb Benjamin Tissoires:
> >> On Jun 15 2016 or thereabouts, Heiner Kallweit wrote:
> >>> Am 14.06.2016 um 23:49 schrieb Benjamin Tissoires:
> On
From: Hayes Wang
Date: Thu, 16 Jun 2016 10:55:16 +0800
> These patches fix some known issues.
Series applied, thanks.
--
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
In set_speed(), BMCR_RESET would be set when the flag of PHY_RESET
is set. Use BMCR_RESET to replace testing the flag of PHY_RESET.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
29 matches
Mail list logo