On Tue, Apr 21, 2015 at 6:56 PM, Jan Kaisrlik wrote:
> From: Jan Kaisrlik
>
> This patch adds a function which helps to connect net device
> to DSA switch based on mii_bus and netdev.
>
> The switch parameters of the switch are configured in fill_platform_data().
> Currently, the configuration da
Hi Rajeev,
> -Original Message-
> From: rajeev kumar [mailto:rajeevkumar.li...@gmail.com]
> Sent: Tuesday, April 21, 2015 10:22 PM
> To: Praveen Murali
> Cc: Ricardo Ribalda Delgado; linux-usb@vger.kernel.org; ba...@ti.com;
> min...@mina86.com
> Subject: Re: usb: gadget: g_multi does not wo
On 22/04/15 05:17, Peter Chen wrote:
> On Tue, Apr 21, 2015 at 10:34:01AM +0300, Roger Quadros wrote:
>> On 21/04/15 09:04, Peter Chen wrote:
>>>
On 20/04/15 06:05, Peter Chen wrote:
> On Tue, Apr 14, 2015 at 01:41:47PM +0300, Roger Quadros wrote:
>> This is an attempt to centra
+ Mathias and David.
Hi Mathias,
Please help to review this patch.
Thanks
Jincan
On Sun, Apr 19, 2015 at 11:46:12AM +0800, Zhuang Jin Can wrote:
> Some usb3 devices may not support usb3 lpm well.
> The patch adds a sysfs to enable/disable u1 or u2 of the port.The
> settings apply to both before
On Wed, Apr 22, 2015 at 10:33:24AM +0300, Roger Quadros wrote:
> On 22/04/15 05:17, Peter Chen wrote:
> > On Tue, Apr 21, 2015 at 10:34:01AM +0300, Roger Quadros wrote:
> >> On 21/04/15 09:04, Peter Chen wrote:
> >>>
>
> On 20/04/15 06:05, Peter Chen wrote:
> > On Tue, Apr 14, 2015
Samsung has just released a portable USB3 SSD, coming in a very small
and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
already used by the pl2303 USB serial driver and the Palm Visor driver
for the Samsung I330 phone cradle. Having pl2303 or visor pick up this
device ID result
Hello.
On 4/22/2015 1:14 PM, Jason A. Donenfeld wrote:
Samsung has just released a portable USB3 SSD, coming in a very small
and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
already used by the pl2303 USB serial driver and the Palm Visor driver
for the Samsung I330 phone c
On Wed, Apr 22, 2015 at 12:14:05PM +0200, Jason A. Donenfeld wrote:
> Samsung has just released a portable USB3 SSD, coming in a very small
> and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
> already used by the pl2303 USB serial driver and the Palm Visor driver
> for the Sam
On 21 April 2015 at 23:51, Alan Stern wrote:
> Anyway, you're suggesting that drivers should never override sysfs
> attribute values. But there doesn't seem to be any other way to
> implement the kernel's policy that wakeup should be enabled by default
> for all keyboard devices.
I just doubt if
Samsung has just released a portable USB3 SSD, coming in a very small
and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
already used by the Palm Visor driver for the Samsung I330 phone cradle.
Having pl2303 or visor pick up this device ID results in conflicts with
the usb-stora
This phone is already supported by the visor driver.
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/pl2303.c | 1 -
drivers/usb/serial/pl2303.h | 4
2 files changed, 5 deletions(-)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 829604d..f5257af 10064
On Wed, Apr 22, 2015 at 01:20:38PM +0200, Johan Hovold wrote:
> On Wed, Apr 22, 2015 at 12:14:05PM +0200, Jason A. Donenfeld wrote:
> > Samsung has just released a portable USB3 SSD, coming in a very small
> > and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
> > already used b
On 22/04/15 12:22, Peter Chen wrote:
> On Wed, Apr 22, 2015 at 10:33:24AM +0300, Roger Quadros wrote:
>> On 22/04/15 05:17, Peter Chen wrote:
>>> On Tue, Apr 21, 2015 at 10:34:01AM +0300, Roger Quadros wrote:
On 21/04/15 09:04, Peter Chen wrote:
>
>>
>> On 20/04/15 06:05, Peter C
On Wed, Apr 22, 2015 at 2:38 PM, Greg Kroah-Hartman
wrote:
> I'd bet this is really a pl2303 device, given that the visor driver was
> just a "dumb" pipe to the device and the pilot sync tools never cared
> about baud rates and the like, so odds are the visor entry should be
> removed.
In the lat
This phone is actually a pl2303 device, and is already supported there.
Signed-off-by: Jason A. Donenfeld
---
drivers/usb/serial/visor.c | 2 --
drivers/usb/serial/visor.h | 1 -
2 files changed, 3 deletions(-)
diff --git a/drivers/usb/serial/visor.c b/drivers/usb/serial/visor.c
index bf2bd40..
Samsung has just released a portable USB3 SSD, coming in a very small
and nice form factor. Its USB ID is 04e8:8001, which unfortunately is
already used by the pl2303 driver for the Samsung I330 phone cradle.
Having pl2303 pick up this device ID results in conflicts with the
usb-storage driver, whi
On Wed, Apr 22, 2015 at 02:42:20PM +0200, Jason A. Donenfeld wrote:
> On Wed, Apr 22, 2015 at 2:38 PM, Greg Kroah-Hartman
> wrote:
> > I'd bet this is really a pl2303 device, given that the visor driver was
> > just a "dumb" pipe to the device and the pilot sync tools never cared
> > about baud ra
On Tue, Apr 21, 2015 at 01:46:36PM +0300, Roger Quadros wrote:
> On 21/04/15 11:08, Maxime Ripard wrote:
> > On Tue, Apr 21, 2015 at 12:49:54PM +0300, Roger Quadros wrote:
> >> On 20/04/15 15:35, Mathias Nyman wrote:
> >>> Hi
> >>>
> >>> On 02.04.2015 15:23, Roger Quadros wrote:
> As xhci_hcd
On Wed, Apr 22, 2015 at 02:38:00PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 22, 2015 at 01:20:38PM +0200, Johan Hovold wrote:
> > On Wed, Apr 22, 2015 at 12:14:05PM +0200, Jason A. Donenfeld wrote:
> > > Samsung has just released a portable USB3 SSD, coming in a very small
> > > and nice form
On Wed, 22 Apr 2015, Praveen Murali wrote:
> > > -Original Message-
> > > From: Ricardo Ribalda Delgado [mailto:ricardo.riba...@gmail.com]
> > > Sent: Tuesday, April 21, 2015 1:33 AM
> > > To: Praveen Murali
> > > Cc: linux-usb@vger.kernel.org; ba...@ti.com; min...@mina86.com
> > > Subject
On Wed, Apr 22, 2015 at 02:35:09PM +0200, Jason A. Donenfeld wrote:
> Samsung has just released a portable USB3 SSD, coming in a very small
> and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
> already used by the Palm Visor driver for the Samsung I330 phone cradle.
> Having pl
On Wed, Apr 22, 2015 at 04:20:39PM +0200, Johan Hovold wrote:
> On Wed, Apr 22, 2015 at 02:38:00PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Apr 22, 2015 at 01:20:38PM +0200, Johan Hovold wrote:
> > > On Wed, Apr 22, 2015 at 12:14:05PM +0200, Jason A. Donenfeld wrote:
> > > > Samsung has just re
On Wed, Apr 22, 2015 at 04:58:44PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 22, 2015 at 04:20:39PM +0200, Johan Hovold wrote:
> > On Wed, Apr 22, 2015 at 02:38:00PM +0200, Greg Kroah-Hartman wrote:
> > > On Wed, Apr 22, 2015 at 01:20:38PM +0200, Johan Hovold wrote:
> > > > On Wed, Apr 22, 201
On Wed, 22 Apr 2015, Tom Yan wrote:
> On 21 April 2015 at 23:51, Alan Stern wrote:
> > Anyway, you're suggesting that drivers should never override sysfs
> > attribute values. But there doesn't seem to be any other way to
> > implement the kernel's policy that wakeup should be enabled by default
On Wed, Apr 22, 2015 at 11:28:29AM -0400, Alan Stern wrote:
> On Wed, 22 Apr 2015, Tom Yan wrote:
>
> > On 21 April 2015 at 23:51, Alan Stern wrote:
> > > Anyway, you're suggesting that drivers should never override sysfs
> > > attribute values. But there doesn't seem to be any other way to
> >
The USB PCI quirks code gets built into the kernel whenever CONFIG_PCI
is enabled, even if CONFIG_USB is not set. This can cause unnecessary
messages to show up in the kernel log, such as "CONFIG_USB_XHCI_HCD is
turned off, defaulting to EHCI" (which makes no sense when the kernel
has been configu
On Wed, 22 Apr 2015, Greg KH wrote:
> > Index: usb-4.0/drivers/hid/hid-logitech-dj.c
> > ===
> > --- usb-4.0.orig/drivers/hid/hid-logitech-dj.c
> > +++ usb-4.0/drivers/hid/hid-logitech-dj.c
> > @@ -990,6 +990,7 @@ static int logi_dj_p
2015-04-21 17:51 GMT+00:00 Florian Fainelli :
> On 21/04/15 10:39, Andrew Lunn wrote:
I would however say that sysfs is the wrong API. The linux network
stack uses netlink for most configuration activities. So i would
suggest adding a netlink binding to DSA, and place the code in
>>>
On Wed, Apr 22, 2015 at 04:14:33PM +, Jan Kaisrlik wrote:
> 2015-04-21 17:51 GMT+00:00 Florian Fainelli :
> > On 21/04/15 10:39, Andrew Lunn wrote:
> I would however say that sysfs is the wrong API. The linux network
> stack uses netlink for most configuration activities. So i would
>
On Wed, Apr 22, 2015 at 12:15:36PM -0400, Alan Stern wrote:
> On Wed, 22 Apr 2015, Greg KH wrote:
>
> > > Index: usb-4.0/drivers/hid/hid-logitech-dj.c
> > > ===
> > > --- usb-4.0.orig/drivers/hid/hid-logitech-dj.c
> > > +++ usb-4.0/dr
On Wed, 22 Apr 2015, Greg KH wrote:
> > > But this device isn't always a keyboard. For example, mine works with a
> > > mouse. It's a "universal receiver", you can't know what type of HID
> > > device is plugged into it until it connects to it. I don't mind making
> > > it auto wakeup, if that
On Wed, Apr 22, 2015 at 02:22:44PM -0400, Alan Stern wrote:
> On Wed, 22 Apr 2015, Greg KH wrote:
>
> > > > But this device isn't always a keyboard. For example, mine works with a
> > > > mouse. It's a "universal receiver", you can't know what type of HID
> > > > device is plugged into it until
Getting phys by index instead of phy names so that we do
not have to create a naming scheme when multiple phys are present
Signed-off-by: Arun Ramamurthy
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/usb/host/ohci-platform.c | 69 ++--
1 file c
Getting phys by index instead of phy names so that we do
not have to create a naming scheme when multiple phys
are present
Signed-off-by: Arun Ramamurthy
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/usb/host/ehci-platform.c | 69 ++--
1 file c
Most of the phy providers use "select" to enable GENERIC_PHY. Since select
is only recommended when the config is not visible, GENERIC_PHY is changed
an invisible option. To maintain consistency, all phy providers are changed
to "select" GENERIC_PHY and all non-phy drivers use "depends on" when the
This patch set adds a new API to get phy by index when multiple
phys are present. This patch is based on discussion with Arnd Bergmann
about dt bindings for multiple phys.
History:
v1:
- Removed null pointers on Dmitry's suggestion
- Improved documentation in commit messages
- Exporte
Some generic drivers, such as ehci, may use multiple phys and for such
drivers referencing phy(s) by name(s) does not make sense. Instead of
inventing new naming schemes and using custom code to iterate through them,
such drivers are better of using nameless phy bindings and using this newly
introd
Why is drivers/usb/Makefile even read when CONFIG_USB is not set?
Won't it make more sense to throw the line
obj-$(CONFIG_PCI) += usb/
from drivers/Makfile?
On Wed, Apr 22, 2015 at 7:11 PM, Alan Stern wrote:
> The USB PCI quirks code gets built into the kernel whenever CONFIG_PCI
> is enabled, e
> > >
> > > Oh, okay, I didn't realize that.
> > >
> > > Is there a reasonable way to enable wakeup only when the driver
> > > learns that a keyboard is connected? Where would the driver do this?
> >
> > I don't know if the driver ever "knows" this, as you can pair lots of
> > different devices
On Wed, Apr 22, 2015 at 03:42:32PM +0300, Roger Quadros wrote:
> > So we will have a separate drd fsm file, and the CONFIG_USB_OTG
> > and CONFIG_USB_OTG_FSM are not needed to be defined, right?
> >
>
> for drd case CONFIG_USB_OTG_FSM is definitely not needed.
> I'm not sure if we can operate dua
Hello Everyone,
I'm newbie to driver development & have a question on CDC NCM gadget driver.
When I load the module g_ncm.ko on the target board
and execute "lsusb" on host, there is some delay in response.
(about 5-10 seconds)
However, if I trim the string as shown below (in code changes),
"lsu
I'm not saying that the kernel shouldn't initialize the attributes or
have a default. But it should only set the default when the attribute
is initialized (It doesn't even matter to me whether it's enabled or
disabled).
It's just there should not be further manipulation from the kernel
(e.g. devic
>
> I'm not saying that the kernel shouldn't initialize the attributes or have a
> default.
> But it should only set the default when the attribute is initialized (It
> doesn't
> even matter to me whether it's enabled or disabled).
>
> It's just there should not be further manipulation from t
https://bugs.freedesktop.org/show_bug.cgi?id=90041
Because udev's work would get overrided if there's further
manipulation. So if you want your udev rule to work, you have to make
sure you run a trigger command after the module is loaded or reloaded.
This would happen for all types of devices if th
On 23/04/15 04:52, Peter Chen wrote:
> On Wed, Apr 22, 2015 at 03:42:32PM +0300, Roger Quadros wrote:
>>> So we will have a separate drd fsm file, and the CONFIG_USB_OTG
>>> and CONFIG_USB_OTG_FSM are not needed to be defined, right?
>>>
>>
>> for drd case CONFIG_USB_OTG_FSM is definitely not neede
Hi Bjørn
> This cannot possibly be necessary. Pointing to the toplevel "COPYING"
> file should be more than enough, if anything at all.
>
> And BTW, the same goes for the tools/usb/usbip/COPYING that seems to
> have snuck in somehow. I also wonder a bit about the AUTHORS file
both
> places. W
46 matches
Mail list logo
