Hi,
Peter Chen writes:
>> Peter Chen writes:
>> >> >> So far, I haven't seen anybody talking about real USB OTG (the spec)
>> >> >> when they say OTG. Usually they just mean "a method for swapping
>> >> >> between
>> >> >> host and peripheral roles, but we really don't want all the extra cost
On Wed, Jun 22, 2016 at 09:51:19AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> >> >> >> > So, unless we use OTG FSM defined in OTG spec, we should not
> >> >> >> > mention
> >> >> >> > "OTG" in Linux, right?
> >> >> >>
> >> >> >> to avoid confusion with the terminology, yes. Wi
Hi Felipe,
On 22/06/16 09:56, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
>>> Peter Chen writes:
>>> So far, I haven't seen anybody talking about real USB OTG (the spec)
>>> when they say OTG. Usually they just mean "a method for swapping between
>>> host and peripheral role
On Tue, Jun 21, 2016 at 7:52 PM, Ben Dooks wrote:
> The usbhs_write32 function is not used outside of the rcar3.c
> file, so fix the following sparse warning by making it static:
>
> drivers/usb/renesas_usbhs/rcar3.c:26:6: warning: symbol 'usbhs_write32' was
> not declared. Should it be static?
>
On Wed, Jun 22, 2016 at 09:56:22AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> >> Peter Chen writes:
> >> >> >> So far, I haven't seen anybody talking about real USB OTG (the spec)
> >> >> >> when they say OTG. Usually they just mean "a method for swapping
> >> >> >> between
>
Hi,
Peter Chen writes:
>> >> >> >> > So, unless we use OTG FSM defined in OTG spec, we should not
>> >> >> >> > mention
>> >> >> >> > "OTG" in Linux, right?
>> >> >> >>
>> >> >> >> to avoid confusion with the terminology, yes. With that settled,
>> >> >> >> let's
>> >> >> >> figure out how yo
Hi,
Peter Chen writes:
>> >> >> >> So far, I haven't seen anybody talking about real USB OTG (the spec)
>> >> >> >> when they say OTG. Usually they just mean "a method for swapping
>> >> >> >> between
>> >> >> >> host and peripheral roles, but we really don't want all the extra
>> >> >> >> cos
Hi,
Mathieu Malaterre writes:
> On Tue, Jun 21, 2016 at 7:52 PM, Ben Dooks wrote:
>> The usbhs_write32 function is not used outside of the rcar3.c
>> file, so fix the following sparse warning by making it static:
>>
>> drivers/usb/renesas_usbhs/rcar3.c:26:6: warning: symbol 'usbhs_write32' was
Hi,
Roger Quadros writes:
> For the real use case, some Carplay platforms need it.
Carplay does *NOT* rely on OTG. Apple has its own proprietary and
closed
specification which is not OTG-compliant.
>>>
>>> Yes, it is not OTG-compliant
Hi,
Felix Hädicke writes:
> Introduces a new FunctionFS descriptor flag named
> FUNCTIONFS_ALL_CTRL_RECIP. When this flag is enabled, control requests,
> which are not explicitly directed to an interface or endpoint, can be
> handled.
>
> This allows FunctionFS userspace drivers to process non-s
Hi,
Felix Hädicke writes:
> It can sometimes be necessary for gadget drivers to process non-standard
> control requests, which host devices can send without having sent
> USB_REQ_SET_CONFIGURATION.
got an example?
--
balbi
signature.asc
Description: PGP signature
On 22/06/16 11:14, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> For the real use case, some Carplay platforms need it.
>
> Carplay does *NOT* rely on OTG. Apple has its own proprietary and
> closed
> specification which is not OTG-compliant.
>
Hello,
> Hi,
>
> Felix Hädicke writes:
> > It can sometimes be necessary for gadget drivers to process non-standard
> > control requests, which host devices can send without having sent
> > USB_REQ_SET_CONFIGURATION.
>
> got an example?
There are Android Open Accessory devices which do so. The
Hello,
> Hi,
>
> Felix Hädicke writes:
> > Introduces a new FunctionFS descriptor flag named
> > FUNCTIONFS_ALL_CTRL_RECIP. When this flag is enabled, control requests,
> > which are not explicitly directed to an interface or endpoint, can be
> > handled.
> >
> > This allows FunctionFS userspace
On 21 June 2016 at 23:26, Rob Herring wrote:
> On Tue, Jun 21, 2016 at 10:11:17AM +0800, Peter Chen wrote:
>> On Mon, Jun 20, 2016 at 11:16:07AM -0500, Rob Herring wrote:
>> > On Mon, Jun 20, 2016 at 07:26:51PM +0800, Peter Chen wrote:
>> > > On Fri, Jun 17, 2016 at 12:16:48PM -0500, Rob Herring w
Hi Oliver,
On Tue, Jun 21, 2016 at 10:43:05PM +0200, Oliver Neukum wrote:
> On Tue, 2016-06-21 at 16:58 +0300, Heikki Krogerus wrote:
> > On Tue, Jun 21, 2016 at 03:08:52PM +0200, Oliver Neukum wrote:
> >
> > > The firmware will surely want to display something. So it is possible
> > > that we s
Hi,
"Felix Hädicke" writes:
>> > Introduces a new FunctionFS descriptor flag named
>> > FUNCTIONFS_ALL_CTRL_RECIP. When this flag is enabled, control requests,
>> > which are not explicitly directed to an interface or endpoint, can be
>> > handled.
>> >
>> > This allows FunctionFS userspace driv
On Tue, Jun 21, 2016 at 10:25:05PM +0200, Oliver Neukum wrote:
> On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote:
> > +What: /sys/class/typec//supported_data_roles
> > +Data: June 2016
> > +Contact: Heikki Krogerus
> > +Description:
> > + Lists the US
Hi Guenter,
On Tue, Jun 21, 2016 at 03:25:55PM -0700, Guenter Roeck wrote:
> On Tue, Jun 21, 2016 at 05:51:49PM +0300, Heikki Krogerus wrote:
> > Hi,
> >
> > I'm considering all the RFCs I send after v1 as v2 (I don't remember
> > how many I send). Hope this is OK and hope there is nothing big
>
Hi again,
Felipe Balbi writes:
> [ Unknown signature status ]
>
> Hi,
>
> "Felix Hädicke" writes:
>>> > Introduces a new FunctionFS descriptor flag named
>>> > FUNCTIONFS_ALL_CTRL_RECIP. When this flag is enabled, control requests,
>>> > which are not explicitly directed to an interface or end
On Wed, Jun 22, 2016 at 12:50:16PM +0300, Heikki Krogerus wrote:
> On Tue, Jun 21, 2016 at 10:25:05PM +0200, Oliver Neukum wrote:
> > On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote:
> > > +What: /sys/class/typec//supported_data_roles
> > > +Data: June 2016
> > > +Contact
On Wed, 2016-06-22 at 12:31 +0300, Heikki Krogerus wrote:
Hi,
> > Now correct me, if I am misreading the spec. I am sure the system
> > will boot unless it needs ridiculous amounts of power, but
> > will we see anything on the screen? As far as I can tell the spec
> > actually says that you canno
On Wed, 2016-06-22 at 12:50 +0300, Heikki Krogerus wrote:
> On Tue, Jun 21, 2016 at 10:25:05PM +0200, Oliver Neukum wrote:
> > On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote:
> > > +What: /sys/class/typec//supported_data_roles
> > > +Data: June 2016
> > > +Contact:
fixed in linux-next, but in linux-next-20160616 there was a
different splat (index 2 out of range instead of index -1 out of range)
in drivers/usb/host/ehci-hub.c:889:34. I got asked to report here.
That last splat persists until at least linux-next-20160622.
Is there anything else you need?
R
Hello,
> > I am developing a driver, which I would like to implement using
> > FunctionFS, for using the Android Open Accessory protocol on
> > non-Android devices. These accessories send some non-standard control
> > requests which are described here:
> > https://source.android.com/devices/access
On Wed, 2016-06-22 at 13:03 +0300, Heikki Krogerus wrote:
> On Wed, Jun 22, 2016 at 12:50:16PM +0300, Heikki Krogerus wrote:
>
> > But if the port is DRP, we will always be able to swap the data role
> > between DFP and UFP.
>
> Just to clarify: DRP as it's defined in Type-C spec < 1.2 means the
> This is actually not for a f_accessory replacement. The control requests are
> sent when the device is in any other gadget mode, for sending metadata and to
> trigger switching to Open Accessory Gadget Mode.
>
> The Accessory mode itself can be handled very easily with f_serial (or a very
> s
On Wed, Jun 22, 2016 at 12:08:57PM +0200, Oliver Neukum wrote:
> On Wed, 2016-06-22 at 12:31 +0300, Heikki Krogerus wrote:
>
> Hi,
>
> > > Now correct me, if I am misreading the spec. I am sure the system
> > > will boot unless it needs ridiculous amounts of power, but
> > > will we see anything
Hi,
"Felix Hädicke" writes:
>> This is actually not for a f_accessory replacement. The control
>> requests are sent when the device is in any other gadget mode, for
>> sending metadata and to trigger switching to Open Accessory Gadget
>> Mode.
>>
>> The Accessory mode itself can be handled very
On Wed, Jun 22, 2016 at 12:14:55PM +0200, Oliver Neukum wrote:
> On Wed, 2016-06-22 at 12:50 +0300, Heikki Krogerus wrote:
> > On Tue, Jun 21, 2016 at 10:25:05PM +0200, Oliver Neukum wrote:
> > > On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote:
> > > > +What: /sys/class/typec//sup
On 06/22/2016 02:51 AM, Heikki Krogerus wrote:
Hi Guenter,
On Tue, Jun 21, 2016 at 03:25:55PM -0700, Guenter Roeck wrote:
On Tue, Jun 21, 2016 at 05:51:49PM +0300, Heikki Krogerus wrote:
Hi,
I'm considering all the RFCs I send after v1 as v2 (I don't remember
how many I send). Hope this is OK
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: d178023ba59940c022fcd0be5b65a0b328fa368a [13/16] usb: core: add power
sequence handling for USB devices
config: i386-defconfig (attached as .config)
c
On Wed, 2016-06-22 at 14:44 +0300, Heikki Krogerus wrote:
> If our port is DRD (which would be DRP in the port controller spec),
> the supported_power_roles will list:
>
> device, host
>
> And the power role, if the port is Source only, the
> supported_power_roles will list:
>
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: 210f01d924a442bc83b11f8bb2c0ee6845fa2e20 [9/16] power: pwrseq: change
common helpers as generic
config: x86_64-allyesdebian (attached as .config)
comp
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: d178023ba59940c022fcd0be5b65a0b328fa368a [13/16] usb: core: add power
sequence handling for USB devices
config: sh-titan_defconfig (attached as .confi
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: d178023ba59940c022fcd0be5b65a0b328fa368a [13/16] usb: core: add power
sequence handling for USB devices
config: blackfin-BF526-EZBRD_defconfig (attach
On Wed, Jun 22, 2016 at 03:47:03PM +0200, Oliver Neukum wrote:
> On Wed, 2016-06-22 at 14:44 +0300, Heikki Krogerus wrote:
> > If our port is DRD (which would be DRP in the port controller spec),
> > the supported_power_roles will list:
> >
> > device, host
> >
> > And the power role, if
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: 210f01d924a442bc83b11f8bb2c0ee6845fa2e20 [9/16] power: pwrseq: change
common helpers as generic
config: blackfin-TCM-BF537_defconfig (attached as .con
t last splat persists until at least linux-next-20160622.
>
> Is there anything else you need?
Please try 4.7-rc4.
Alan Stern
--
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
to report here.
> That last splat persists until at least linux-next-20160622.
>
> Is there anything else you need?
Is this still in 4.7-rc4? All of the reported ubsan fixes for USB
should now be in there.
If not, can you provide the full "splat" here?
thanks,
greg k-h
--
To un
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb
add_pwrseq_for_usb
head: 236dd95c9a8872af797cc504ea9d0fe74b8c55d3
commit: 210f01d924a442bc83b11f8bb2c0ee6845fa2e20 [9/16] power: pwrseq: change
common helpers as generic
config: sparc-defconfig (attached as .config)
compiler
Hi Rupesh,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit a8425292816ceaa8c49e29d2114e85d85a73e080
Author: Rupesh Tatiya
Date: Tue Apr 14 16:36:55 2015 +0530
usb: Enable LPM for USB 2.01
On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
> Hi Rupesh,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit a8425292816ceaa8c49e29d2114e85d85a73e080
> Author: Rupesh
On Wed, 22 Jun 2016, Joseph Salisbury wrote:
> Hi Rupesh,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit a8425292816ceaa8c49e29d2114e85d85a73e080
> Author: Rupesh Tatiya
> Date: Tu
On 06/22/2016 12:57 AM, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 10 May 2016 05:09 AM, David Lechner wrote:
The initial use for this is for PHYs that have a mode related to USB OTG.
There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting
in the USB PHY to override OTG VBUS
From 2261f0ea15690623dcefd71b8aaaea6089b16468 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Wed, 16 Mar 2016 14:16:08 -0500
Subject: [PATCH] phy: da8xx-usb: new driver for DA8xx SoC USB PHY
This is a new phy driver for the SoC USB controllers on the TI DA8xx
family of microcontrollers. The
From b0ae5eeba849b49f82980218a374c6d3f06487b8 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Thu, 24 Mar 2016 01:38:54 -0500
Subject: [PATCH] ARM: davinci: da8xx: Add CFGCHIP syscon platform
declaration.
The CFGCHIP registers are used by a number of devices, so using a syscon
device to sha
From 53c9b38e0a7860e51ce7bdfe6d4f1d83cf2394a5 Mon Sep 17 00:00:00 2001
From: David Lechner
Date: Wed, 16 Mar 2016 14:25:23 -0500
Subject: [PATCH] ARM: davinci: da8xx: Add USB PHY platform declaration
There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the
platform device declar
On 05/25/2016 06:15 AM, Sekhar Nori wrote:
On Tuesday 10 May 2016 10:14 PM, David Lechner wrote:
On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first c
On Wed, 2016-06-22 at 17:38 +0300, Heikki Krogerus wrote:
> On Wed, Jun 22, 2016 at 03:47:03PM +0200, Oliver Neukum wrote:
> > On Wed, 2016-06-22 at 14:44 +0300, Heikki Krogerus wrote:
> > > If our port is DRD (which would be DRP in the port controller spec),
> > > the supported_power_roles will li
This is a new phy driver for the SoC USB controllers on the TI DA8xx
family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
The USB 2.0 PHY also allows overriding the VBUS and ID pins.
Signed-off-by: David Lechner
Reviewed-by: Sekhar Nori
---
Just one small change here. Changed "
of range instead of index -1 out of range)
> > in drivers/usb/host/ehci-hub.c:889:34. I got asked to report here.
> > That last splat persists until at least linux-next-20160622.
> >
> > Is there anything else you need?
>
> Is this still in 4.7-rc4? All of the report
inux-next, but in linux-next-20160616 there was a
> > > different splat (index 2 out of range instead of index -1 out of range)
> > > in drivers/usb/host/ehci-hub.c:889:34. I got asked to report here.
> > > That last splat persists until at least linux-next-20160622.
&g
Even if the /dev/hidg* chardev is automatically created, one
has to guess which one belongs to which function. In the case
of multiple HID functions, or maybe even multiple peripherals,
this becomes difficult.
Add the major/minor to configfs (read-only) to allow looking
up (or even creating) the r
On Fri, Jun 17, 2016 at 12:25 PM, Andy Lutomirski wrote:
> 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 ; Andy Lutomi
Hi,
On Tue, Jun 21, 2016 at 05:51:50PM +0300, Heikki Krogerus wrote:
> The purpose of USB Type-C connector class is to provide
> unified interface for the user space to get the status and
> basic information about USB Type-C connectors on a system,
> control over data role swapping, and when USB P
> -Original Message-
> From: Andy Lutomirski [mailto:l...@amacapital.net]
> Sent: Wednesday, June 22, 2016 3:44 PM
> To: Limonciello, Mario
> Cc: Greg KH ; Andrew Lutomirski
> ; Mathias Nyman ; USB
> list ; Mathias Nyman
> ; Dominguez, Jared
>
> Subject: Re: Minor xhci issues (failed to p
> -Original Message-
> From: Limonciello, Mario
> Sent: Tuesday, June 14, 2016 5:27 PM
> To: 'David Miller' ; pali.ro...@gmail.com
> Cc: gre...@linuxfoundation.org; and...@lunn.ch;
> hayesw...@realtek.com; linux-ker...@vger.kernel.org;
> net...@vger.kernel.org; linux-usb@vger.kernel.org;
>
On Wed, Jun 22, 2016 at 3:06 PM, wrote:
>> -Original Message-
>> From: Andy Lutomirski [mailto:l...@amacapital.net]
>> Sent: Wednesday, June 22, 2016 3:44 PM
>> To: Limonciello, Mario
>> Cc: Greg KH ; Andrew Lutomirski
>> ; Mathias Nyman ; USB
>> list ; Mathias Nyman
>> ; Dominguez, Jare
> >
> > I've only got WD15 and TB15's.
>
> Do you have a link to the product page for these? I'll probably buy
> one in the next couple of weeks, but I can only find the WD15, not the
> TB15. From the FAQ
> (http://www.dell.com/support/article/us/en/04/SLN301105), it looks
> like the TB15 suppor
<https://bugzilla.kernel.org/show_bug.cgi?id=120361>. GregKH asked if
> > > > this was fixed in linux-next, but in linux-next-20160616 there was a
> > > > different splat (index 2 out of range instead of index -1 out of range)
> > > > in drivers/usb/host/
On Wed, Jun 22, 2016 at 3:29 PM, wrote:
>> >
>> > I've only got WD15 and TB15's.
>>
>> Do you have a link to the product page for these? I'll probably buy
>> one in the next couple of weeks, but I can only find the WD15, not the
>> TB15. From the FAQ
>> (http://www.dell.com/support/article/us/e
On Wed, Jun 22, 2016 at 04:21:58PM -0700, Andy Lutomirski wrote:
On Wed, Jun 22, 2016 at 3:29 PM, wrote:
>
> I've only got WD15 and TB15's.
Do you have a link to the product page for these? I'll probably buy
one in the next couple of weeks, but I can only find the WD15, not the
TB15. From t
On Wed, Jun 22, 2016 at 4:35 PM, D. Jared Dominguez
wrote:
> On Wed, Jun 22, 2016 at 04:21:58PM -0700, Andy Lutomirski wrote:
>>
>> On Wed, Jun 22, 2016 at 3:29 PM, wrote:
>
> I've only got WD15 and TB15's.
Do you have a link to the product page for these? I'll probably
64 matches
Mail list logo
