On 3/28/2016 10:38 PM, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Allow for platforms that have a reset controller driver in place to bring
> the USB IP out of reset.
>
> Signed-off-by: Dinh Nguyen
> Cc: John Youn
> ---
> drivers/usb/dwc2/core.h |1 +
> drivers/usb/
On 7 April 2016 at 12:56, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
>> On Wed, Apr 06, 2016 at 01:25:06PM +0300, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Peter Chen writes:
>>> > On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
>>> >> Peter Chen writes:
>>> >> > On Wed, Apr
HI
"Du, Changbin" writes:
>> before I review your patches, one comment
>>
>> changbin...@intel.com writes:
>> > From: "Du, Changbin"
>> >
>> > The first patch removed unnecessary checking for debugfs api call;
>> > The second patch fix a memory leak issue;
>> > The third patch add one new entr
> before I review your patches, one comment
>
> changbin...@intel.com writes:
> > From: "Du, Changbin"
> >
> > The first patch removed unnecessary checking for debugfs api call;
> > The second patch fix a memory leak issue;
> > The third patch add one new entry to debufs.
> >
> > Du, Changbin (3)
Hi,
Kirill Dronov writes:
> I'm working on USB device bringup on Intel E3800 – based board. DWC3
> core configured as DRD in device mode. The only connected device phy
> is SMSC 3310 (USB2 ULPI). DWC3 core version is 2.10A. Gadget zero
> driver can be loaded, but device enumeration fails: device
Hi,
David Laight writes:
> From: Felipe Balbi
>> Sent: 06 April 2016 14:25
>> If we _know_ length is 0, we can just return 1 early.
>
> Does that happen often enough to be an optimisation?
> Looks like a mispredicted branch to me.
it's not optimizing, it's cleaning it up. Code looks a little cl
changbin...@intel.com writes:
> From: "Du, Changbin"
>
no commit log == no commit, sorry
> Signed-off-by: Du, Changbin
> ---
> drivers/usb/dwc3/debugfs.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/dwc3/debugfs.c b/drivers/usb/dwc3/debugfs.c
> index 071b286..2d4f39
Hi,
before I review your patches, one comment
changbin...@intel.com writes:
> From: "Du, Changbin"
>
> The first patch removed unnecessary checking for debugfs api call;
> The second patch fix a memory leak issue;
> The third patch add one new entry to debufs.
>
> Du, Changbin (3):
> usb: dwc
On 06/04/16 19:53, Greg KH wrote:
On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote:
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
Kernel driver in use: x
Hi,
Greg Kroah-Hartman writes:
> On Wed, Apr 06, 2016 at 01:19:04PM +0300, Felipe Balbi wrote:
>> > What happened to getting internal help in designing this api? This
>> > shouldn't be my job :)
>>
>> I looked at this Baolu but, at least to me, it's unclear what you're
>> hinting here. Sure, t
Hi,
Peter Chen writes:
>> >> > In below change of usb_gadget_vbus_draw(), already can get charger
>> >> > type via usb_charger_get_type().
>> >> >
>> >> > static inline int usb_gadget_vbus_draw(struct usb_gadget *gadget,
>> >> > unsigned mA) {
>> >> > + enum usb_charger_type type;
>> >> >
Hi,
Peter Chen writes:
> On Wed, Apr 06, 2016 at 01:25:06PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Peter Chen writes:
>> > On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
>> >> Peter Chen writes:
>> >> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
>> >> >>
On Wed, Apr 06, 2016 at 04:58:03PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Jun Li writes:
> >> >> >> > Since we already have get_charger_type callback at usb_charger
> >> >> >> > structure, why we still need this API at usb_gadget_ops?
> >> >> >>
> >> >> >> In case some users want to get charger
On Wed, Apr 06, 2016 at 01:25:06PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> > On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
> >> Peter Chen writes:
> >> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
> >> >> Peter Chen writes:
> >> >> > On Fr
On 04/06/2016 08:10 PM, Johan Hovold wrote:
> As Joe already said, we generally don't want indentation-only changes to
> existing code. Just try to stick to the style of the driver (even if
> it's inconsistent at times).
>
Hm, I don't get it. I understand that white-space-only changes are
discou
On Wed, Apr 06, 2016 at 01:19:04PM +0300, Felipe Balbi wrote:
> > What happened to getting internal help in designing this api? This
> > shouldn't be my job :)
>
> I looked at this Baolu but, at least to me, it's unclear what you're
> hinting here. Sure, the API is a bit odd in that we register a
On Wed, 6 Apr 2016, Dmitry Torokhov wrote:
> >>> [ 685.425634] atkbd serio0: Unknown key pressed (translated set 2,
> >>> code 0xa8 on isa0060/serio0).
> >>> [ 685.425648] atkbd serio0: Use 'setkeycodes e028 ' to make it
> >>> known.
> >>>
> >>> Known issue?
> >>>
> >>> Do you need more input?
On Wed, 6 Apr 2016, Greg KH wrote:
> On Wed, Apr 06, 2016 at 04:08:04PM +0300, Mathias Nyman wrote:
> > We don't want to runtime suspend a bus if there is an event pending.
> > The roothub on a NEC uPD720200 host with a single USB3 device connected
> > might go back to runtime suspend immediately
On Wed, Apr 06, 2016 at 11:44:05PM +0800, changbin...@intel.com wrote:
> From: "Du, Changbin"
>
> Signed-off-by: Du, Changbin
> ---
You need a changelog entry in order for a patch to be able to be
accepted.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-us
Hi,
I'm getting a kernel oops when I plug some smartphone via USB to my
laptop, which is currently running the v4.6-rc2.
The problem seems to be caused by a81cf9799ad7 ("cdc-acm: implement
put_char() and flush_chars()").
A simple NULL pointer check prevents the crash, but since I have no
use of
On Wed, Apr 06, 2016 at 04:08:04PM +0300, Mathias Nyman wrote:
> We don't want to runtime suspend a bus if there is an event pending.
> The roothub on a NEC uPD720200 host with a single USB3 device connected
> might go back to runtime suspend immediately after runtime resume as
> hub might not yet
On Wed, Apr 06, 2016 at 07:58:36PM +0200, Grigori Goronzy wrote:
> On 04/02/2016 07:29 PM, Joe Perches wrote:
> > Most of the whitespace only changes are undesired.
>
> Well, the style wasn't very consistent. I think consistency is
> important. So I took the liberty of deciding for one style and
On 04/03/2016 06:03 PM, Karl Palsson wrote:
>
> Grigori Goronzy wrote:
>> The status bit was found with USB captures of the Windows
>> driver and some luck. Tested on CH340G and CH341A.
>
> By my reversing, bit 0x4, is "multiple status changes since last
> interrupt"
>
Thanks, I can add the def
On 04/02/2016 07:29 PM, Joe Perches wrote:
> Most of the whitespace only changes are undesired.
>
Well, the style wasn't very consistent. I think consistency is
important. So I took the liberty of deciding for one style and stuck to it.
> Multi-line statements here are using alignment to
> ope
On Wed, Apr 06, 2016 at 06:13:42PM +0530, Kishon Vijay Abraham I wrote:
> On Friday 04 March 2016 09:49 PM, Thierry Reding wrote:
[...]
> > +struct tegra124_xusb_fuse_calibration {
> > + u32 hs_curr_level[3];
> > + u32 hs_iref_cap;
> > + u32 hs_term_range_adj;
> > + u32 hs_squelch_level;
>
On Tue, Apr 05, 2016 at 03:10:16PM -0600, Stephen Warren wrote:
> On 04/05/2016 08:44 AM, Thierry Reding wrote:
> > On Wed, Mar 16, 2016 at 11:59:44AM -0600, Stephen Warren wrote:
> > > On 03/04/2016 09:19 AM, Thierry Reding wrote:
> > > > From: Thierry Reding
> > > >
> > > > Extend the binding t
On Wed, Apr 6, 2016 at 3:27 AM, Sedat Dilek wrote:
> On Wed, Apr 6, 2016 at 11:35 AM, Sedat Dilek wrote:
>> On Wed, Apr 6, 2016 at 11:27 AM, Sedat Dilek wrote:
>>> Hi,
>>>
>>> I cannot use cursor up and down on my notebook and see this in my dmesg.
>>>
>>> [ 685.425634] atkbd serio0: Unknown ke
On Wed, Apr 06, 2016 at 09:15:26AM +0800, Peter Chen wrote:
> > > No, this comment is common one, but only for SW detection. Eg, when
> > > the PMIC tells you it is a SDP, you can't notify to charger IC about
> > > 500mA at once, you need to do it after host allows you to do it.
> > Note that thi
From: Felipe Balbi
> Sent: 06 April 2016 14:25
> If we _know_ length is 0, we can just return 1 early.
Does that happen often enough to be an optimisation?
Looks like a mispredicted branch to me.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of
Alan Stern writes:
> On Wed, 6 Apr 2016, Bjørn Mork wrote:
>> Alan Stern writes:
>> > On Wed, 6 Apr 2016, Mathias Nyman wrote:
>> >
>> >> We don't want to runtime suspend a bus if there is an event pending.
>> >> The roothub on a NEC uPD720200 host with a single USB3 device connected
>> >> might
On Wed, 6 Apr 2016, Bjørn Mork wrote:
> Alan Stern writes:
>
> > On Wed, 6 Apr 2016, Mathias Nyman wrote:
> >
> >> We don't want to runtime suspend a bus if there is an event pending.
> >> The roothub on a NEC uPD720200 host with a single USB3 device connected
> >> might go back to runtime suspe
From: "Du, Changbin"
The first patch removed unnecessary checking for debugfs api call;
The second patch fix a memory leak issue;
The third patch add one new entry to debufs.
Du, Changbin (3):
usb: dwc3: make dwc3_debugfs_init return value be void
usb: dwc3: free dwc->regset on dwc3_debugfs_
From: "Du, Changbin"
Debugfs init failure is not so important. We can continue our job on
this failure. Also no need to check debugfs_create_file call results.
Signed-off-by: Du, Changbin
---
drivers/usb/dwc3/core.c| 10 +-
drivers/usb/dwc3/debug.h | 6 +++---
drivers/usb/dwc3/d
From: "Du, Changbin"
For DWC3 USB controller, the Global Debug Queue/FIFO Space Available
Register(GDBGFIFOSPACE) can be used to dump FIFO/Queue available space.
This can be used to check some special issues, like whether data is
successfully copied from memory to fifo when a trb is blocked.
Sig
From: "Du, Changbin"
Signed-off-by: Du, Changbin
---
drivers/usb/dwc3/debugfs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/dwc3/debugfs.c b/drivers/usb/dwc3/debugfs.c
index 071b286..2d4f397 100644
--- a/drivers/usb/dwc3/debugfs.c
+++ b/drivers/usb/dwc3/debugfs.c
@@ -657,
Added support for Gemalto's Cinterion PH8 and AHxx products
with 2 RmNet Interfaces and products with 1 RmNet + 1 USB Audio interface.
The RmNet and USB Audio interfaces are blacklisted because they will be
handled by other drivers.
In addition some minor renaming and formatting.
Signed-off-by:
Alan Stern writes:
> On Wed, 6 Apr 2016, Mathias Nyman wrote:
>
>> We don't want to runtime suspend a bus if there is an event pending.
>> The roothub on a NEC uPD720200 host with a single USB3 device connected
>> might go back to runtime suspend immediately after runtime resume as
>> hub might n
On Wed, 6 Apr 2016, Michal Nazarewicz wrote:
> On Tue, Apr 05 2016, Alan Stern wrote:
> > Suppose one usb_function is carrying out an I/O operation while
> > another one in the same config gets a Set-Interface request from the
> > host.
>
> That cannot happen. A single instance of mass_storage c
On Wed, 6 Apr 2016, Mathias Nyman wrote:
> We don't want to runtime suspend a bus if there is an event pending.
> The roothub on a NEC uPD720200 host with a single USB3 device connected
> might go back to runtime suspend immediately after runtime resume as
> hub might not yet see any port changes
Robert Dobrowolski writes:
> From: Rafal Redzimski
>
> Current implementation updates the mtu size and notify cdc_ncm
> device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram
> size change instead of changing rx_urb_size.
>
> Whenever mtu is being changed, datagram size should also be
Adding vendor specific directories in phy to group
phy drivers under their respective vendor umbrella.
Also updated the MAINTAINERS file to reflect the correct
directory structure for phy drivers.
Signed-off-by: Vivek Gautam
Acked-by: Heiko Stuebner
Acked-by: Viresh Kumar
---
Changes from v1:
Although ULPI phy is currently being used by tusb1210,
there can be other consumers too in future. So move this
to the includes path for phy.
Signed-off-by: Vivek Gautam
---
{drivers => include/linux}/phy/ulpi_phy.h | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename {drivers => include
Hi.
I'm working on USB device bringup on Intel E3800 – based board. DWC3
core configured as DRD in device mode. The only connected device phy is
SMSC 3310 (USB2 ULPI). DWC3 core version is 2.10A. Gadget zero driver
can be loaded, but device enumeration fails: device is detected by host,
speed
Hi,
Jun Li writes:
>> >> >> > Since we already have get_charger_type callback at usb_charger
>> >> >> > structure, why we still need this API at usb_gadget_ops?
>> >> >>
>> >> >> In case some users want to get charger type at gadget level.
>> >> >>
>> >> > Why gadget needs to know charger type?
Hi
> -Original Message-
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Wednesday, April 06, 2016 8:56 PM
> To: Jun Li ; Baolin Wang ; Peter
> Chen
> Cc: Greg KH ; Sebastian Reichel
> ; Dmitry Eremin-Solenikov ; David
> Woodhouse ; Peter Chen ;
> Alan Stern ; r.bald...@samsung.com;
Hi Kishon,
On Wed, Apr 6, 2016 at 5:51 AM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote:
>> Hi,
>>
>>
>> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>>
>>> On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote:
Addin
Hi Al,
Lars-Peter Clausen writes:
> In the current implementation functionfs generates a EFAULT for async read
> operations if the read buffer size is larger than the URB data size. Since
> a application does not necessarily know how much data the host side is
> going to send it typically suppli
Hi,
The following two patches are tiny simplifications
two count_trbs() and count_sg_trbs_needed() which
make the code slightly easier to read.
Felipe Balbi (2):
usb: xhci: ring: simplify count_trbs() a little bit
usb: xhci: ring: simplify count_sg_trbs_needed()
drivers/usb/host/xhci-ring.c
If we _know_ length is 0, we can just return 1 early.
While at that, we're also adding a comment
referencing the location where the 64KiB boundary is
mentioned in the xhci spec. This will prevent people
from thinking this isn't necessary in the future.
We're also changing the bitwise-and operator
we _know_ that for_each_sg() will only iterate over
number of mapped sgs, so there's no need to count
full_len and break out when it reaches zero.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-ring.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/drive
From: Lu Baolu
This patch fixes some wild pointers produced by xhci_mem_cleanup.
These wild pointers will cause system crash if xhci_mem_cleanup()
is called twice.
Reported-and-tested-by: Pengcheng Li
Signed-off-by: Lu Baolu
Cc: sta...@vger.kernel.org
Signed-off-by: Mathias Nyman
---
drivers
From: Yoshihiro Shimoda
This patch fixes an issue that cannot work if R-Car Gen2/3 run on
above 4GB physical memory environment to use a quirk XHCI_NO_64BIT_SUPPORT.
Cc:
Signed-off-by: Yoshihiro Shimoda
Reviewed-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-plat.c
Give USB3 devices a better chance to enumerate at USB 3 speeds if
they are connected to a suspended host.
Solves an issue with NEC uPD720200 host hanging when partially
enumerating a USB3 device as USB2 after host controller runtime resume.
Cc:
Tested-by: Mike Murdoch
Signed-off-by: Mathias Nyma
From: Yoshihiro Shimoda
On some xHCI controllers (e.g. R-Car SoCs), the AC64 bit (bit 0) of
HCCPARAMS1 is set to 1. However, the xHCs don't support 64-bit
address memory pointers actually. So, in this case, this driver should
call dma_set_coherent_mask(dev, DMA_BIT_MASK(32)) in xhci_gen_setup().
PCI hotpluggable xhci controllers such as some Alpine Ridge solutions will
remove the xhci controller from the PCI bus when the last USB device is
disconnected.
Add a flag to indicate that the host is being removed to avoid queueing
configure_endpoint commands for the dropped endpoints.
For PCI ho
We don't want to runtime suspend a bus if there is an event pending.
The roothub on a NEC uPD720200 host with a single USB3 device connected
might go back to runtime suspend immediately after runtime resume as
hub might not yet see any port changes in resume.
Prevent this by checking if there is a
Hi Greg
These xhci fixes solve various small issues such as:
* USB 3 device enumeration issues after runtime resume seen on NEC hosts
* Add a PCI ID and needed quirk for a new controller
* Remove extra 10 seconds driver timeouts on PCI hotplugged xhcis
* R-Car SoC xhci quirks to solve their DM
From: Rafal Redzimski
Broxton B0 also requires XHCI_PME_STUCK_QUIRK.
Adding PCI device ID for Broxton B and adding to quirk.
Cc:
Signed-off-by: Rafal Redzimski
Signed-off-by: Robert Dobrowolski
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-pci.c | 4 +++-
1 file changed, 3 insertio
Hi,
Jun Li writes:
>> >> On 6 April 2016 at 15:19, Peter Chen wrote:
>> >> > On Fri, Apr 01, 2016 at 03:21:50PM +0800, Baolin Wang wrote:
>> >> >>
>> >> >> @@ -563,6 +564,8 @@ struct usb_gadget_ops {
>> >> >> struct usb_ep *(*match_ep)(struct usb_gadget *,
>> >> >> s
Hi,
On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote:
> Hi,
>
>
> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote:
>>> Adding vendor specific directories in phy to group
>>> phy drivers under their respective ve
> -Original Message-
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Wednesday, April 06, 2016 8:22 PM
> To: Jun Li ; Baolin Wang ; Peter
> Chen
> Cc: Greg KH ; Sebastian Reichel
> ; Dmitry Eremin-Solenikov ; David
> Woodhouse ; Peter Chen ;
> Alan Stern ; r.bald...@samsung.com; Y
Hi,
On Friday 04 March 2016 09:49 PM, Thierry Reding wrote:
> From: Thierry Reding
>
> Add a new driver for the XUSB pad controller found on NVIDIA Tegra SoCs.
> This hardware block used to be exposed as a pin controller, but it turns
> out that this isn't a good fit. The new driver and DT bindi
Hello.
On 4/6/2016 9:44 AM, Lu Baolu wrote:
+struct intel_mux_dev {
+ struct device *dev;
+ char*extcon_name;
+ char*cable_name;
+ int (*cable_set_cb)(struct intel_mux_dev *mux);
+ int (*cable_unset_cb)(struct intel
Hi,
(please make sure to break your lines at
80-characters. Documentation/email-clients.txt has several tips for
different email clients ;-))
"Du, Changbin" writes:
>> > @@ -648,6 +687,12 @@ int dwc3_debugfs_init(struct dwc3 *dwc)
>> >goto err1;
>> >}
>> >
>> > + file = debugfs
Hi,
Jun Li writes:
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Baolin Wang
>> Sent: Wednesday, April 06, 2016 6:47 PM
>> To: Peter Chen
>> Cc: Felipe Balbi ; Greg KH ;
>> Sebastian Reichel ; Dmitry Eremin-Solen
Hi
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Baolin Wang
> Sent: Wednesday, April 06, 2016 6:47 PM
> To: Peter Chen
> Cc: Felipe Balbi ; Greg KH ;
> Sebastian Reichel ; Dmitry Eremin-Solenikov
> ; David Woodhouse
On Sat, 2 Apr 2016 19:07:16 +0200
Grigori Goronzy wrote:
> With the new reinitialization method, configuring parity, different
> frame lengths and different stop bit settings work as expected on
> both CH340G and CH341A. This has been extensively tested with a
> logic analyzer.
>
> Tested-by:
On Sat, 2 Apr 2016 19:07:10 +0200
Grigori Goronzy wrote:
> Signed-off-by: Grigori Goronzy
> ---
> drivers/usb/serial/ch341.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index c73808f..43e4594 100644
> ---
Hi
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Wednesday, April 06, 2016 7:31 PM
> To: Jun Li
> Cc: ba...@kernel.org; gre...@linuxfoundation.org; s...@kernel.org;
> dbarysh...@gmail.com; dw...@infradead.org; peter.c...@freescale.com;
> st...@rowland.ha
From: Rafal Redzimski
Current implementation updates the mtu size and notify cdc_ncm
device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram
size change instead of changing rx_urb_size.
Whenever mtu is being changed, datagram size should also be
updated.
Cc:
Signed-off-by: Rafal Redz
> > This can be used to check some special issues, like whether data is
> > successfully copied from memory to fifo when a trb is blocked.
> >
> > Signed-off-by: Du, Changbin
> > ---
> > drivers/usb/dwc3/core.h| 5 +
> > drivers/usb/dwc3/debugfs.c | 45
> +
On 6 April 2016 at 16:26, Jun Li wrote:
> Hi
>
>> + */
>> +static enum usb_charger_type
>> +usb_charger_get_type_by_others(struct usb_charger *uchger) {
>> + if (uchger->type != UNKNOWN_TYPE)
>> + return uchger->type;
>> +
>> + if (uchger->psy) {
>> + union power_su
Hi John,
Felipe Balbi writes:
> Felipe Balbi writes:
>> Synopsys Databook says we should move link to U0
>> before issuing a Start Transfer command. We could
>> require the gadget driver to call
>> usb_gadget_wakeup() however I feel that changing all
>> gagdget drivers to keep track of Link Sta
On 6 April 2016 at 15:19, Peter Chen wrote:
> On Fri, Apr 01, 2016 at 03:21:50PM +0800, Baolin Wang wrote:
>>
>> @@ -563,6 +564,8 @@ struct usb_gadget_ops {
>> struct usb_ep *(*match_ep)(struct usb_gadget *,
>> struct usb_endpoint_descriptor *,
>>
On Wed, Apr 6, 2016 at 12:33 PM, Jiri Kosina wrote:
> On Wed, 6 Apr 2016, Sedat Dilek wrote:
>
>> >> I cannot use cursor up and down on my notebook and see this in my dmesg.
>> >>
>> >> [ 685.425634] atkbd serio0: Unknown key pressed (translated set 2,
>> >> code 0xa8 on isa0060/serio0).
>> >> [
On Wed, 6 Apr 2016, Sedat Dilek wrote:
> >> I cannot use cursor up and down on my notebook and see this in my dmesg.
> >>
> >> [ 685.425634] atkbd serio0: Unknown key pressed (translated set 2,
> >> code 0xa8 on isa0060/serio0).
> >> [ 685.425648] atkbd serio0: Use 'setkeycodes e028 ' to make it
On Wed, Apr 6, 2016 at 11:35 AM, Sedat Dilek wrote:
> On Wed, Apr 6, 2016 at 11:27 AM, Sedat Dilek wrote:
>> Hi,
>>
>> I cannot use cursor up and down on my notebook and see this in my dmesg.
>>
>> [ 685.425634] atkbd serio0: Unknown key pressed (translated set 2,
>> code 0xa8 on isa0060/serio0)
Hi,
Peter Chen writes:
> On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
>> Peter Chen writes:
>> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
>> >> Peter Chen writes:
>> >> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
>> >> > +
>> >> >> +sta
Hi,
Peter Chen writes:
> On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
>> Peter Chen writes:
>> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
>> >> Peter Chen writes:
>> >> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
>> >> > +
>> >> >> +sta
Hi,
Greg Kroah-Hartman writes:
> On Wed, Apr 06, 2016 at 02:44:55PM +0800, Lu Baolu wrote:
>> Hi,
>>
>> On 03/14/2016 11:27 AM, Greg Kroah-Hartman wrote:
>> > On Mon, Mar 14, 2016 at 09:09:22AM +0800, Lu Baolu wrote:
>> >> On 03/11/2016 08:06 AM, Greg Kroah-Hartman wrote:
>> >>> On Tue, Mar 08,
Hi,
Greg Kroah-Hartman writes:
>> On 03/11/2016 07:57 AM, Greg Kroah-Hartman wrote:
>> > On Thu, Mar 10, 2016 at 01:39:43PM +0100, Oliver Neukum wrote:
>> >> On Tue, 2016-03-08 at 15:53 +0800, Lu Baolu wrote:
>> >>
>> >>> diff --git a/Documentation/ABI/testing/sysfs-bus-platform
>> >>> b/Docume
On 04/06/2016 10:52 AM, Pavel Machek wrote:
Hi!
Lets say we have
/sys/class/pattern/lp5533::0
/sys/class/pattern/software::0
/sys/class/led/n900::red ; default trigger "lp5533::0:0"
/sys/class/led/n900::green ; default trigger "lp5533::0:1"
/sys/class/led/n900::blue ; default trigger "lp5533:
On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote:
> SETUP:
>
> i7 16GB Computer.
>
> 1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB controller:
> Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
> Kernel driver in use: xhci_hcd
>
> 2 x USB3 to
On Wed, Apr 06, 2016 at 01:58:52PM +0800, Lu Baolu wrote:
> Hi,
>
> On 03/11/2016 07:57 AM, Greg Kroah-Hartman wrote:
> > On Thu, Mar 10, 2016 at 01:39:43PM +0100, Oliver Neukum wrote:
> >> On Tue, 2016-03-08 at 15:53 +0800, Lu Baolu wrote:
> >>
> >>> diff --git a/Documentation/ABI/testing/sysfs-b
On Wed, Apr 06, 2016 at 02:44:55PM +0800, Lu Baolu wrote:
> Hi,
>
> On 03/14/2016 11:27 AM, Greg Kroah-Hartman wrote:
> > On Mon, Mar 14, 2016 at 09:09:22AM +0800, Lu Baolu wrote:
> >> On 03/11/2016 08:06 AM, Greg Kroah-Hartman wrote:
> >>> On Tue, Mar 08, 2016 at 03:53:44PM +0800, Lu Baolu wrote:
Hi!
> >As I see it the current blinking support then would be one special case of a
> >pattern.
> >As a consequence once having pattern support we might be able to switch
> >users of blinking
> >to pattern and remove the blinking support.
>
> Let's split patterns related discussion into a separ
Hi!
> > We would probably need additional op in the LED core : color_set.
> >
> > Having the color set to nonzero value would signify the the three LED
> > class devices are in sync and that setting a trigger on any of them
> > applies to the remaining two ones. It would have to be considered
> >
Hi
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Baolin Wang
> Sent: Friday, April 01, 2016 3:22 PM
> To: ba...@kernel.org; gre...@linuxfoundation.org; s...@kernel.org;
> dbarysh...@gmail.com; dw...@infradead.org
> Cc:
Hi!
> >Lets say we have
> >
> >/sys/class/pattern/lp5533::0
> >/sys/class/pattern/software::0
> >
> >/sys/class/led/n900::red ; default trigger "lp5533::0:0"
> >/sys/class/led/n900::green ; default trigger "lp5533::0:1"
> >/sys/class/led/n900::blue ; default trigger
On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
> Peter Chen writes:
> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
> >> Peter Chen writes:
> >> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
> >> > +
> >> >> +static struct attribute *usb_charger_
On Wed, Apr 06, 2016 at 11:05:26AM +0300, Felipe Balbi wrote:
> Peter Chen writes:
> > On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
> >> Peter Chen writes:
> >> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
> >> > +
> >> >> +static struct attribute *usb_charger_
Peter Chen writes:
> On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
>> Peter Chen writes:
>> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
>> > +
>> >> +static struct attribute *usb_charger_attrs[] = {
>> >> + &dev_attr_sdp_current.attr,
>> >> + &dev_attr_dcp_curr
On Wed, Apr 06, 2016 at 10:38:23AM +0300, Felipe Balbi wrote:
> Peter Chen writes:
> > On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
> > +
> >> +static struct attribute *usb_charger_attrs[] = {
> >> + &dev_attr_sdp_current.attr,
> >> + &dev_attr_dcp_current.attr,
> >> + &dev_att
Peter Chen writes:
> On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
> +
>> +static struct attribute *usb_charger_attrs[] = {
>> +&dev_attr_sdp_current.attr,
>> +&dev_attr_dcp_current.attr,
>> +&dev_attr_cdp_current.attr,
>> +&dev_attr_aca_current.attr,
>> +&dev_a
On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
+
> +static struct attribute *usb_charger_attrs[] = {
> + &dev_attr_sdp_current.attr,
> + &dev_attr_dcp_current.attr,
> + &dev_attr_cdp_current.attr,
> + &dev_attr_aca_current.attr,
> + &dev_attr_charger_type.attr,
>
On Fri, Apr 01, 2016 at 03:21:50PM +0800, Baolin Wang wrote:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb charger c
On 06/04/16 09:46, Peter Chen wrote:
> On Tue, Apr 05, 2016 at 04:48:19PM +0300, Roger Quadros wrote:
>> Peter,
>>
>> On 05/04/16 15:52, Roger Quadros wrote:
>>> Peter,
>>>
>>> On 05/04/16 11:52, Peter Chen wrote:
On Thu, Mar 31, 2016 at 12:41:19PM +0300, Roger Quadros wrote:
> If usb/otg-
97 matches
Mail list logo
