Am 29.03.2016 um 23:43 schrieb Pavel Machek:
> Hi!
>
>>> First, please Cc me on RGB color support.
>>>
Add generic support for RGB Color LED's.
Basic idea is to use enum led_brightness also for the hue and saturation
color components.This allows to implement the color
Hi Felipe,
Thank you for the patch!
> Sent: Tuesday, March 29, 2016 7:11 PM
< snip >
> static const struct xhci_plat_priv xhci_plat_renesas_rcar_gen2 = {
> .type = XHCI_PLAT_TYPE_RENESAS_RCAR_GEN2,
> .firmware_name = XHCI_RCAR_FIRMWARE_NAME_V1,
> + .init_quirk =
Hi,
> The ohci-platform and ehci-platform drivers already perform their own
root-hub and bus resets.
I don't understand the sentence clearly.
Synopsis control VERSION: DesignWare Cores USB2.0 Host-AHB Controller, Version
2.98a
The synopsis has the three source clocks for EHCI Host
> -Original Message-
> From: Baolin Wang [mailto:baolin.w...@linaro.org]
> Sent: Tuesday, March 29, 2016 5:49 PM
> To: Jun Li
> Cc: Peter Chen ; Felipe Balbi ;
> Greg KH ; Sebastian Reichel
On Tue, Mar 29, 2016 at 10:23:14AM -0700, Mark Brown wrote:
> On Mon, Mar 28, 2016 at 03:13:51PM +0800, Peter Chen wrote:
> > On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang wrote:
>
> > > > I am afraid I still not find the user (udc driver) for this framework,
> > > > I would
> > > > like
On Tue, Mar 29, 2016 at 05:42:50PM +0100, reggie macdonald wrote:
> Hi I made a bug report on bugzilla and was told to forward it to this email.
>
> Please see this thread: https://bbs.archlinux.org/viewtopic.php?id=210446
>
> for current information related to the problem.
>
> To summarise:
>
On Tue, Mar 29, 2016 at 10:15:41PM +0300, Светослав Нейков wrote:
> //adding cc to linux-usb ml
>
> 2016-03-29 7:55 GMT+03:00 Peter Chen :
> > Would you please try below patch to see if it works for you:
>
> With the patch applied the code enters "ci_udc_vbus_session", but
Hi,
On 03/29/2016 05:17 PM, Lipengcheng wrote:
> Hi
>Thanks Baolu very much!
>Because of the reason usb3 module can not be used, it will affect the
> strong of usb3 module;
> 1, the xhci control is suspend and resume, why to re-allocate memory?
Some controllers need to set
Hi!
> > One driver for this extension was the idea of triggers using color
> > to visualize states etc.
> > Therefore it's not only about userspace controlling the color.
> > As a trigger is bound to a led_classdev we need a led_classdev
> > representing a RGB LED device.
> >
> > And ok: If
Hi!
> > First, please Cc me on RGB color support.
> >
> >> Add generic support for RGB Color LED's.
> >>
> >> Basic idea is to use enum led_brightness also for the hue and saturation
> >> color components.This allows to implement the color extension w/o
> >> changes to struct led_classdev.
> >>
Am 29.03.2016 um 12:05 schrieb Pavel Machek:
> On Tue 2016-03-01 22:36:12, Heiner Kallweit wrote:
>> Export a function to convert HSV color values to RGB.
>> It's intended to be called by drivers for RGB LEDs.
>>
>> Signed-off-by: Heiner Kallweit
>> ---
>> v2:
>> - move hsv
On Mon, Mar 28, 2016 at 03:13:51PM +0800, Peter Chen wrote:
> On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang wrote:
> > > I am afraid I still not find the user (udc driver) for this framework, I
> > > would
> > > like to see how udc driver block the enumeration until the charger
> > >
On 28.03.2016 09:13, Rajesh Bhagat wrote:
-Original Message-
From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
Sent: Wednesday, March 23, 2016 7:52 PM
To: Rajesh Bhagat
Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
On Tue, Mar 29, 2016 at 05:24:59PM +0200, Marcel Ziswiler wrote:
> Hi Thierry
>
> On Fri, 2016-03-04 at 17:19 +0100, Thierry Reding wrote:
> > From: Thierry Reding > >
> >
> > The NVIDIA Tegra XUSB pad controller provides a set of pads, each
> >
The CP2105 is used in the GE Healthcare Remote Alarm Box, with the
Manufacturer ID of 0x1901 and Product ID of 0x0194.
Signed-off-by: Martyn Welch
---
drivers/usb/serial/cp210x.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/cp210x.c
This patch adds support for the GPIO found on the CP2105. Unlike the GPIO
provided by some of the other devices supported by the cp210x driver, the
GPIO on the CP2015 is muxed on pins otherwise used for serial control
lines. The GPIO have been configured in 2 separate banks as the choice to
Hi I made a bug report on bugzilla and was told to forward it to this email.
Please see this thread: https://bbs.archlinux.org/viewtopic.php?id=210446
for current information related to the problem.
To summarise:
Works in windows and also bios/arch options menu but stops working when system
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of tilman
> Sent: Tuesday, March 29, 2016 04:02
> To: linux-usb@vger.kernel.org
> Subject: Re: driver migration
>
> Greg KH writes:
>
> Dear Greg
>
> > > I moved
On 29.03.2016 11:33, Mathias Nyman wrote:
endpoint companion for config 1 interface 0 altsetting 1 ep 131:
using minimum values
Mar 27 21:14:18 hydra kernel: [ 104.306485] usb 3-2: New USB device
found, idVendor=0bc2, idProduct=2312
Mar 27 21:14:18 hydra kernel: [ 104.306490] usb 3-2: New USB
Hi,
On Fri, Mar 18, 2016 at 08:59:48AM +0200, Felipe Balbi wrote:
>
> Hi,
>
> Bin Liu writes:
> > [ text/plain ]
> > Hi,
> >
> > On Fri, Mar 11, 2016 at 6:54 AM, Felipe Balbi
> > wrote:
> >> previously we were using a maximum of 32 TRBs per
>
Hello,
> 4.5.0+, which patches do you have on top of 4.5 vanilla ?
No code patches, just the configuration and dts file for the board.
> Also, can you try this patch:
I tried it, but the result is the same.
Sometimes I can see another entry in the log:
g_serial gadget: suspend
And there is
Le 29/03/2016 11:28, Felipe Balbi a écrit :
> coccicheck found this pattern which could be
> converted to PTR_ERR_OR_ZERO(). No functional
> changes.
>
> Signed-off-by: Felipe Balbi
Acked-by: Nicolas Ferre
Thanks Felipe for having taken
On 29.03.2016 14:21, Sergei Shtylyov wrote:
Hello.
On 3/29/2016 1:47 PM, Mathias Nyman wrote:
commit b37d83a6a414 ("usb: Parse the new USB 3.1 SuperSpeedPlus Isoc
endpoint companion descriptor") caused a regression in 4.6-rc1 and fails
to parse SuperSpeed endpoint companion descriptors.
The
Hello.
On 3/29/2016 1:47 PM, Mathias Nyman wrote:
commit b37d83a6a414 ("usb: Parse the new USB 3.1 SuperSpeedPlus Isoc
endpoint companion descriptor") caused a regression in 4.6-rc1 and fails
to parse SuperSpeed endpoint companion descriptors.
The new SuperSpeedPlus Isoc endpoint companion
Dmitry Osipenko writes:
> 29.03.2016 13:31, Felipe Balbi пишет:
>> Dmitry Osipenko writes:
>>> udc->softconnect should be set regardless of the VBUS state, otherwise
>>> the USB peripheral device, connected during suspend, won't be detected
>>> since
29.03.2016 13:31, Felipe Balbi пишет:
Dmitry Osipenko writes:
udc->softconnect should be set regardless of the VBUS state, otherwise
the USB peripheral device, connected during suspend, won't be detected
since can_pullup() would return false and the UDC won't be enabled.
commit b37d83a6a414 ("usb: Parse the new USB 3.1 SuperSpeedPlus Isoc
endpoint companion descriptor") caused a regression in 4.6-rc1 and fails
to parse SuperSpeed endpoint companion descriptors.
The new SuperSpeedPlus Isoc endpoint companion parsing code incorrectly
decreased the the remaining
Hi Greg
This fixes the regression seen in 4.6-rc2 with USB 3.0 devices.
http://marc.info/?l=linux-usb=145920036421563=2
The first version was sent to usb-next. I failed however to respond to Alans
comments and couldn't make it in time for 4.6-rc1.
This version incudes the changes he proposed.
Dmitry Osipenko writes:
> udc->softconnect should be set regardless of the VBUS state, otherwise
> the USB peripheral device, connected during suspend, won't be detected
> since can_pullup() would return false and the UDC won't be enabled.
>
> Fixes: 252455c40316 (usb: gadget:
Hi,
"Felipe F. Tonello" writes:
> [ text/plain ]
> buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed
> devices.
>
> That caused the OUT endpoint to freeze if the host send any data packet of
> length greater than 256 bytes.
>
> This is an example
these two methods will be used to hide
platform-specific details so we can get rid of
xhci_plat_type_is() in a later patch.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-plat.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
Now that there are no more users for
xhci_plat_type_is(), we can safely remove it.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-plat.c | 3 ---
drivers/usb/host/xhci-plat.h | 18 --
2 files changed, 21 deletions(-)
diff --git
This 6-patch series gets rid of the pointless
xhci_plat_type_is() in favour of a nicer setup where
we initialize function pointers ahead of time using
driver_data. That way we help the code look a little
cleaner and easier to read.
Felipe Balbi (6):
usb: host: xhci: rcar: retire use of
Just like RCAR's init_quirk() we want mvebu's to use
struct usb_hcd * as argument too. This is another
step towards removing xhci_plat_type_is().
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-mvebu.c | 7 ++-
drivers/usb/host/xhci-mvebu.h | 7 +--
We're preparing to remove xhci_plat_type_is() in
favor of a better approach where we define function
pointers ahead of time. This will let us make
assumptions about which platforms we're running on
and which platform-specific functions we should call.
Signed-off-by: Felipe Balbi
xhci_plat_setup() is the rightful place for
xhci_mvebu_mbus_init_quirk(), so let's move it there
in order to make it simpler to get rid of
xhci_plat_type_is() later on.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-plat.c | 15 +--
1 file
Now that the code has been refactored enough,
switching over to using ->plat_start() and
->init_quirk() becomes a very simple patch.
After this patch, there are no further uses for
xhci_plat_type_is() which will be removed in a
follow-up patch.
Signed-off-by: Felipe Balbi
On Tue 2016-03-01 22:36:12, Heiner Kallweit wrote:
> Export a function to convert HSV color values to RGB.
> It's intended to be called by drivers for RGB LEDs.
>
> Signed-off-by: Heiner Kallweit
> ---
> v2:
> - move hsv -> rgb conversion to separate file
> - remove flag
Hi!
First, please Cc me on RGB color support.
> Add generic support for RGB Color LED's.
>
> Basic idea is to use enum led_brightness also for the hue and saturation
> color components.This allows to implement the color extension w/o
> changes to struct led_classdev.
>
> Select LEDS_RGB to
On Tue 2016-03-01 22:28:00, Heiner Kallweit wrote:
> Extend brightness sysfs property handling to deal with monochrome
> and color mode as well.
>
> Signed-off-by: Heiner Kallweit
> ---
> v2:
> - split from patch 1
> v3:
> - moved one change (led_is_off) to patch 1
> v4:
>
On 29 March 2016 at 16:45, Jun Li wrote:
>
>
>> -Original Message-
>> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
>> ow...@vger.kernel.org] On Behalf Of Baolin Wang
>> Sent: Monday, March 28, 2016 2:52 PM
>> To: Peter Chen
>> Cc: Felipe
coccicheck found this pattern which could be
converted to PTR_ERR_OR_ZERO(). No functional
changes.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/phy-qcom-8x16-usb.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
coccicheck found this pattern which could be
converted to PTR_ERR_OR_ZERO(). No functional
changes.
Signed-off-by: Felipe Balbi
---
drivers/usb/gadget/udc/at91_udc.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Hi
Thanks Baolu very much!
Because of the reason usb3 module can not be used, it will affect the strong
of usb3 module;
1, the xhci control is suspend and resume, why to re-allocate memory?
2, whether we can allocate memory for more times, so we can avoid the
problem;
Best
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Baolin Wang
> Sent: Monday, March 28, 2016 2:52 PM
> To: Peter Chen
> Cc: Felipe Balbi ; Greg KH ;
>
On Sat, 26 Mar 2016, Felipe Balbi wrote:
> Peter Griffin writes:
> > On Fri, 25 Mar 2016, Felipe Balbi wrote:
> >> Gregory CLEMENT writes:
> >> >> Peter Griffin writes:
> >> >>> Otherwise generic-xhci and
Greg KH writes:
Dear Greg
> > I moved the initialization and clean up code from the init_callback/release
> > callback to the port_init/port_remove callback.
I am referring to your last posting on Feb 25th:
gkh> Release your port data in the port_remove callback, not the release
gkh>
endpoint companion for config 1 interface 0 altsetting 1 ep 131:
using minimum values
Mar 27 21:14:18 hydra kernel: [ 104.306485] usb 3-2: New USB device
found, idVendor=0bc2, idProduct=2312
Mar 27 21:14:18 hydra kernel: [ 104.306490] usb 3-2: New USB device
strings: Mfr=1, Product=2,
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 +
Hi,
(please, don't top-post)
JB writes:
> [ text/plain ]
> But that's it. On the host side, the device is detected for a brief
> moment - I managed to get the device info, and it looks like the real
> deal:
>
> Gadget Serial v2.4:
>Product ID: 0xa4a7
>
From: Dinh Nguyen
Add the resets property for the 2 USB controllers.
Signed-off-by: Dinh Nguyen
---
arch/arm/boot/dts/socfpga.dtsi |4
arch/arm/boot/dts/socfpga_arria10.dtsi |4
2 files changed, 8
51 matches
Mail list logo