On 05/24/2017 08:10 PM, Badhri Jagan Sridharan wrote:
Thanks comments inline.
On Tue, May 23, 2017 at 7:38 PM, Guenter Roeck wrote:
On 05/23/2017 06:28 PM, Badhri Jagan Sridharan wrote:
User space applications in some cases have the need to enforce a
specific port type(DFP/UFP/DRP). This cha
On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote:
> > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that
> > works with Type-C Port Controller Manager to provide USB
> > Power Delivery and USB Type-C function
On Wed, May 24, 2017 at 08:22:35AM -0700, Guenter Roeck wrote:
> On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote:
> > > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that
> > > works with Type-C Port Contr
Hi Felipe,
On 2017-04-19 01:53, Krzysztof Opasiak wrote:
> On 04/15/2017 03:35 AM, Stefan Agner wrote:
>> Currently qw_sign requires UTF-8 character to set, but returns UTF-16
>> when read. This isn't obvious when simply using cat since the null
>> characters are not visible, but hexdump unveils t
On Wed, May 24, 2017 at 11:34 PM, Alan Stern wrote:
> On Wed, 24 May 2017, Kai-Heng Feng wrote:
>
>> On Wed, May 24, 2017 at 12:43 AM, Alan Stern
>> wrote:
>> >>
>> >> Output of `cat /sys/kernel/debug/usb/usbmon/1u`:
>> >> Runtime PM disabled as attachment.
>> >
>> > When you say "runtime PM dis
On Friday 19 May 2017 07:03 PM, Alexandre Bailon wrote:
> This adds the CPPI 4.1 DMA controller to the USB OTG controller.
>
> Changes since v2:
> - Fixed the the property reg-names (had glue register defined)
> - Removed few useless property
>
> Signed-off-by: Alexandre Bailon
Looks good to me
From: YD Tseng
One of the xHCI host controllers supports both USB 3.1/3.0 extended speed
protocol lists. The content of the lists is shown as below.
In xhci-mem.c, the USB 3.1 speed is parsed first, the min_rev of usb3_rhub
is set as 0x10. And then USB 3.0 is parsed. However, the min_rev of
usb
Update V3 patch
>> + xhci->usb3_rhub.min_rev = 0;
>> + xhci->usb2_rhub.min_rev = 0;
>
> Why set these? Are they not already cleared out at initialization time?
They are already cleared out at initialization, removing these 2 lines.
Thanks,
YD
On Tue, May 23, 2017 at 8:09 PM, Greg KH
On Thu, May 25, 2017 at 11:04:19AM +0300, Heikki Krogerus wrote:
> On Wed, May 24, 2017 at 08:22:35AM -0700, Guenter Roeck wrote:
> > On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote:
> > > On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote:
> > > > Driver for USB Typ
On Tue, 2017-05-23 at 14:00 -0700, Stephen Boyd wrote:
> On 05/23, Fabien Lahoudere wrote:
> > Hi,
> >
> > We investigate on the topic and now our device tree look like:
> >
> > in imx53.dtsi:
> >
> > usbh2: usb@53f80400 {
> > compatible = "fsl,imx53-usb", "fsl,imx27-usb";
> > reg =
Hello,
Le 23/05/2017 à 17:26, David Miller a écrit :
> From: Romain Perier
> Date: Tue, 23 May 2017 10:53:36 +0200
>
>> Hello,
>>
>>
>> Le 23/05/2017 à 09:27, Leon Romanovsky a écrit :
>>> On Mon, May 22, 2017 at 06:48:58PM +0200, Romain Perier wrote:
The PCI pool API is deprecated. This co
On Mon, May 22, 2017 at 09:21:33AM +0800, Chunfeng Yun wrote:
> Hi,
> On Sat, 2017-05-20 at 21:19 +0200, Greg Kroah-Hartman wrote:
> > On Sun, May 21, 2017 at 02:05:31AM +0900, Masahiro Yamada wrote:
> > > The combo of list_empty() and list_first_entry() can be replaced with
> > > list_first_entry_
On Tue, May 16, 2017 at 03:26:10PM +0300, Heikki Krogerus wrote:
> Hi,
>
> This series replaces the current UCSI driver (which was only trying to
> fix the data role of the port to host) with a new driver that registers
> itself to the typec class.
>
> The driver is split in two. The core part is
On 05/16/2017 05:26 AM, Heikki Krogerus wrote:
If USB PD contract is established after creation of the
partner, the power delivery support attribute of the partner
needs to be updated separately. This can be done in
typec_set_pwr_opmode() by checking if the port has already
partner and updating t
On 5/22/2017 8:26 PM, Shyam Sundar S K wrote:
>
> On 5/22/2017 6:49 PM, Mathias Nyman wrote:
>> On 22.05.2017 11:56, Shyam Sundar S K wrote:
>>> Hi Mathias,
>>>
>>>
>>> On 5/19/2017 12:43 PM, Mathias Nyman wrote:
On 18.05.2017 16:46, Alan Stern wrote:
> On Thu, 18 May 2017, Shyam Sundar
On 05/16/2017 05:26 AM, Heikki Krogerus wrote:
UCSI - USB Type-C Connector System Software Interface - is a
specification that defines set of registers and data
structures for controlling the USB Type-C ports. It's
designed for systems where an embedded controller (EC) is in
charge of the USB Typ
On 05/16/2017 05:26 AM, Heikki Krogerus wrote:
Driver for ACPI UCSI interface method. This driver replaces
the previous UCSI driver drivers/usb/misc/ucsi.c.
Signed-off-by: Heikki Krogerus
---
drivers/usb/misc/Kconfig | 26 --
drivers/usb/misc/Makefile | 1 -
drivers/us
On Thu, 25 May 2017, Harald Welte wrote:
> What are you referring-to specifically? We have two distinct issues
> here:
>
> a) the fact that you can "remove" the device (disable the "enable"
>feature), but there is no similar interface for re-enabling the
>"enable" feature (which appears
On 24.05.2017 17:44, Greg KH wrote:
On Wed, May 24, 2017 at 04:11:12PM +0300, Mathias Nyman wrote:
This optimization significantly reduces xhci driver load time.
In ACPI tables the acpi companion port devices are children of
the hub device. The port devices are identified by their port number
r
This is needed in preparation of adding support for omap3 and
later OHCI. The runtime PM will only do something on platforms
that implement it.
Cc: devicet...@vger.kernel.org
Cc: Hans de Goede
Cc: Rob Herring
Cc: Roger Quadros
Cc: Sebastian Reichel
Cc: Yoshihiro Shimoda
Signed-off-by: Tony Li
This driver is no longer needed and can be removed. The reason why
it's safe to remove this driver is that most omap devices don't have a
USB low-speed or full-speed compatible PHY installed and configured
with drivers/mfd/omap-usb-host.c. This means that devices like
beagleboard and pandaboard nee
With the runtime PM implemented for ohci-platform driver, we can
now support omap3 and later OHCI by adding one device tree
property.
Cc: Hans de Goede
Cc: Rob Herring
Cc: Yoshihiro Shimoda
Cc: Sebastian Reichel
Acked-by: Alan Stern
Acked-by: Roger Quadros
Signed-off-by: Tony Lindgren
---
Hi,
Here's v3 of this series.
Regards,
Tony
Changes since v2:
- Ignore pm_runtime_get_sync for remove(), not much we can do there
as noted by Alan Stern
- Add acks
Changes since v1:
On Thu, 25 May 2017, Tony Lindgren wrote:
> This is needed in preparation of adding support for omap3 and
> later OHCI. The runtime PM will only do something on platforms
> that implement it.
>
> Cc: devicet...@vger.kernel.org
> Cc: Hans de Goede
> Cc: Rob Herring
> Cc: Roger Quadros
> Cc: Seb
On Thu, 25 May 2017, Kai-Heng Feng wrote:
> > My mistake; we need to see the information from "lspci -vv -s 00:12.0"
> > with two "v"'s, not just one.
>
> Before wakeup:
> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB
> EHCI Controller (rev 39) (prog-if 20 [EHCI])
> S
On Thu, May 25, 2017 at 12:11:53PM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 25, 2017 at 11:04:19AM +0300, Heikki Krogerus wrote:
> > On Wed, May 24, 2017 at 08:22:35AM -0700, Guenter Roeck wrote:
> > > On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote:
> > > > On Wed, May 24,
Hi John,
On Sat, May 6, 2017 at 7:37 PM, Martin Blumenstingl
wrote:
> USB support in the Meson8 SoCs is provided by a DWC2 controller which
> works with the same settings as Meson8b and GXBB. Using the generic
> "snps,dwc2" binding results in an endless stream of "Overcurrent change
> detected" m
On Thu, May 25, 2017 at 12:48 AM, Guenter Roeck wrote:
> On 05/24/2017 08:10 PM, Badhri Jagan Sridharan wrote:
>>
>> Thanks comments inline.
>>
>> On Tue, May 23, 2017 at 7:38 PM, Guenter Roeck wrote:
>>>
>>> On 05/23/2017 06:28 PM, Badhri Jagan Sridharan wrote:
User space applicat
On Thu, May 25, 2017 at 11:24:20AM -0700, Badhri Jagan Sridharan wrote:
> On Thu, May 25, 2017 at 12:48 AM, Guenter Roeck wrote:
> > On 05/24/2017 08:10 PM, Badhri Jagan Sridharan wrote:
> >>
> >> Thanks comments inline.
> >>
> >> On Tue, May 23, 2017 at 7:38 PM, Guenter Roeck wrote:
> >>>
> >>>
Currently VBUS is turned off while a usb device is detached, and turned
on again by the polling routine. This short period VBUS loss prevents
usb modem to switch mode.
VBUS should be constantly on for host-only mode, so this changes the
driver to not turn off VBUS for host-only mode.
Fixes: 2f3fd
Hi Greg,
Here is just one fix for v4.12-rc3. It fixes a musb regression which happens
since v4.9. I will send a separate backport for v4.9-stable. Please let me know
if any change is needed.
Regards,
-Bin.
---
Bin Liu (1):
usb: musb: dsps: keep VBUS on for host-only mode
drivers/usb/musb/mus
From: Gavin Li
If a stalling TRB is cancelled and NOOP'ed in xhci_handle_cmd_stop_ep(),
finish_td() never gets called to reset the halted endpoint and the
endpoint remains indefinitely stalled. This patch ensures that
xhci_cleanup_halted_endpoint() is called after a TRB completion if the
endpoint
There is some limitation for AMD Promontory xHCI host to
disable USB port function. It will enable USB wake-up function then cause USB
disable port feature to fail.
Workaround this issue on Promontory xHCI host
is clear PORT_WAKE_BITS.
Signed-off-by: Jiahau Chang
---
drivers/usb/host/xhci-hu
On Fri, May 26, 2017 at 1:01 AM, Alan Stern wrote:
> On Thu, 25 May 2017, Kai-Heng Feng wrote:
>
>> > My mistake; we need to see the information from "lspci -vv -s 00:12.0"
>> > with two "v"'s, not just one.
>>
>> Before wakeup:
>> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB
On Fri, May 26, 2017 at 09:44:17AM +0800, Jiahau Chang wrote:
> There is some limitation for AMD Promontory xHCI host to
> disable USB port function. It will enable USB wake-up function then cause USB
> disable port feature to fail.
> Workaround this issue on Promontory xHCI host
> is clear POR
35 matches
Mail list logo
