On 22.10.18 07:42, Peter Chen wrote:
> NXP (Freecale) imx HSIC design has some special requirements, add
> some flags at host code to handle them.
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/chipidea/host.c | 24
> include/linux/usb/chipidea.h | 3 +++
> 2 fil
Hi Peter,
On 23.10.18 08:33, Peter Chen wrote:
>
>> As I already posted when I was testing v1 last week, there is a problem with
>> auto
>> suspend with my LAN9730 chip. I thought it was a problem with the
>> smsc95xx/usbnet driver, but I'm not so sure anymore.
>>
>> So I'd like to figure out
On 22.10.18 07:43, Peter Chen wrote:
> To support imx HSIC, there are some special requirement:
> - The HSIC pad is 1.2v, it may need to supply from external
> - The data/strobe pin needs to be pulled down first, and after
>host mode is initialized, the strobe pin needs to be pulled up
> - Duri
> > diff --git a/drivers/usb/chipidea/host.c b/drivers/usb/chipidea/host.c
> > index d858a82c4f44..d74a13d7c21c 100644
> > --- a/drivers/usb/chipidea/host.c
> > +++ b/drivers/usb/chipidea/host.c
> > @@ -28,6 +28,20 @@ struct ehci_ci_priv {
> > struct regulator *reg_vbus;
> > };
> >
> > +/*
-Paul Eaves
+Paul Elder
On 03/11/18 23:07, Terence Neill wrote:
Hi folks,
Thanks for the replies, I really appreciate them. I've made some progress
on this. I'm new to USB so apologies if the following text is incorrect or
is just bizarre!:
1. The problem with streaming_maxpacket set to 2048
> > + }
> > +
> > + if (data->hsic_pad_regulator) {
> > + ret = regulator_enable(data->hsic_pad_regulator);
> > + if (ret) {
> > + dev_err(dev,
> > + "Fail to enable HSIC pad regula
Hi Terence,
(CC'ing Paul Elder, Kieran Bingham and Felipe Balbi)
On Saturday, 3 November 2018 23:07:33 EET Terence Neill wrote:
> Hi folks,
>
> Thanks for the replies, I really appreciate them. I've made some progress
> on this. I'm new to USB so apologies if the following text is incorrect or
Hi,
Laurent Pinchart writes:
> On Saturday, 3 November 2018 23:07:33 EET Terence Neill wrote:
>> Hi folks,
>>
>> Thanks for the replies, I really appreciate them. I've made some progress
>> on this. I'm new to USB so apologies if the following text is incorrect or
>> is just bizarre!:
>>
>>
Hi,
Thinh Nguyen writes:
> +static void dwc3_dump_gadget_internal_states(struct seq_file *s)
> +{
> + struct dwc3 *dwc = s->private;
> + int num_selects = 16;
> + int i;
> + u32 reg;
> + u64
Hi Felipe
I received a Rock960 board. It has a rk3399 rockchip armv8 processor
with 2 DWC3 controllers. And guess what: it works perfectly fine. No
trickery to get super speed connection in device mode.
So there is something wrong with the up-board, not with the DWC3 driver.
Thanks for you suppo
Hi Felipe,
On Monday, 5 November 2018 14:05:59 EET Felipe Balbi wrote:
> Laurent Pinchart writes:
> > On Saturday, 3 November 2018 23:07:33 EET Terence Neill wrote:
> >> Hi folks,
> >>
> >> Thanks for the replies, I really appreciate them. I've made some
> >> progress on this. I'm new to USB so
Hi,
Laurent Pinchart writes:
> On Monday, 5 November 2018 14:05:59 EET Felipe Balbi wrote:
>> Laurent Pinchart writes:
>> > On Saturday, 3 November 2018 23:07:33 EET Terence Neill wrote:
>> >> Hi folks,
>> >>
>> >> Thanks for the replies, I really appreciate them. I've made some
>> >> progress
Hi Thomas,
Thomas JOURDAN writes:
> I received a Rock960 board. It has a rk3399 rockchip armv8 processor
> with 2 DWC3 controllers. And guess what: it works perfectly fine. No
> trickery to get super speed connection in device mode.
>
> So there is something wrong with the up-board, not with the
Hi Fabio,
On 25.10.18 15:20, Fabio Estevam wrote:
> Hi Frieder,
>
> On Thu, Sep 20, 2018 at 10:52 AM Frieder Schrempf
> wrote:
>>
>> Hi,
>>
>> I have a question concerning the setup for a board with an onboard USB
>> hub. The SoC (i.MX6S) is expected to provide a 12 MHz clock on one of
>> the cl
This series adds drivers and FPGA manager support required
for FT232H based ARRI FPGA configuration adapters.
Patch 1/3 adds FT232H interface driver (for ARRI USB PIDs)
implementing commonly used FTDI USB transfer operations and
ACBUS/MPSSE GPIO controllers. Depending on USB PIDs it creates
platfo
Add SPI bus controller driver for FTDI MPSSE mode. This driver
is supposed to be used together with the FT232H interface driver
for FPGA configuration in drivers/usb/misc/ft232h-intf.c which
adds an mpsse spi platform device describing USB SPI bus with
attached SPI slave devices.
Signed-off-by: An
Add USB interface driver for ARRI FPGA configuration devices based on
FTDI FT232H chip. Depending on USB PID the driver registers different
platform devices describing an FPGA configuration interface.
One FPGA configuration interface type is the usual SPI bus with
additional control and status GPI
Add FPGA manager driver for loading ARRI Altera FPGAs via fast
passive parallel (FPP) interface using FTDI FT232H chip.
Signed-off-by: Anatolij Gustschin
---
drivers/fpga/Kconfig | 7 +
drivers/fpga/Makefile| 1 +
drivers/fpga/ftdi-fifo-fpp.c | 594 +++
Hi Wolfram,
Do you have any comments on these patches?
Thanks
Ajay
> nvpublic
> -Original Message-
> From: Andy Shevchenko
> Sent: Monday, October 29, 2018 5:43 AM
> To: Ajay Gupta
> Cc: w...@the-dreams.de; heikki.kroge...@linux.intel.com; p...@axentia.se;
> linux-usb@vger.kernel.org; li
Hi Greg,
On 11/2/2018 11:26 PM, Greg KH wrote:
> On Fri, Nov 02, 2018 at 06:47:38PM -0700, Thinh Nguyen wrote:
>> Move Synopsys HAPS platform device IDs to pci_ids.h.
> Why? pci_ids.h, at the top of the file, says to not add new entries to
> the file.
Yes, I notice. However, I want to reference
++ linux-usb
++ Greg
On 11/2/2018 6:47 PM, Thinh Nguyen wrote:
> Synopsys USB 3.x host HAPS platform has a class code of
> PCI_CLASS_SERIAL_USB_XHCI, and xhci driver can claim it. However, these
> devices should use dwc3-haps driver. Set driver_override to dwc3-haps
> for these platforms.
>
> Sign
On Mon, Nov 5, 2018 at 10:19 AM Anatolij Gustschin wrote:
Hi Anatolij,
>
> This series adds drivers and FPGA manager support required
> for FT232H based ARRI FPGA configuration adapters.
Is this a repost or a new version of this patchset? If it's a repost,
you could note that. If there are ch
On Mon, Nov 05, 2018 at 06:46:26PM +, Thinh Nguyen wrote:
> Hi Greg,
>
> On 11/2/2018 11:26 PM, Greg KH wrote:
> > On Fri, Nov 02, 2018 at 06:47:38PM -0700, Thinh Nguyen wrote:
> >> Move Synopsys HAPS platform device IDs to pci_ids.h.
> > Why? pci_ids.h, at the top of the file, says to not ad
Hi Felipe,
On 11/5/2018 4:16 AM, Felipe Balbi wrote:
> Hi,
>
> Thinh Nguyen writes:
>> +static void dwc3_dump_gadget_internal_states(struct seq_file *s)
>> +{
>> +struct dwc3 *dwc = s->private;
>> +int num_selects = 16;
>> +int i;
>>
On 11/4/2018 11:11 PM, Felipe Balbi wrote:
> Both flags are used for the same purpose in dwc3: appending an extra
> TRB at the end to deal with controller requirements. By combining both
> flags into one, we make it clear that the situation is the same and
> that they should be treated equally.
>
>
Hi Alan,
On Mon, 5 Nov 2018 12:52:03 -0600
Alan Tull at...@kernel.org wrote:
>On Mon, Nov 5, 2018 at 10:19 AM Anatolij Gustschin wrote:
>
>Hi Anatolij,
>
>>
>> This series adds drivers and FPGA manager support required
>> for FT232H based ARRI FPGA configuration adapters.
>
>Is this a repost o
Hi Li
On 2018-11-04 23:19, Jun Li wrote:
Hi Angus
-Original Message-
From: Angus Ainslie
Sent: 2018年11月1日 21:53
To: Jun Li
Subject: USB Type C ptn5110
Hi Li,
We have a custom PCB that has a PTN5110 on it. The board can power
from the
USB C no problem but we are starting to look in
Hi Anatolij,
I love your patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.20-rc1 next-20181105]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Anatolij,
I love your patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.20-rc1 next-20181105]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi,
Thinh Nguyen writes:
> @@ -2250,7 +2250,7 @@ static int dwc3_gadget_ep_reclaim_completed_trb(struct
> dwc3_ep *dep,
>> * with one TRB pending in the ring. We need to manually clear HWO bit
>> * from that TRB.
>> */
>> -if ((req->zero || req->unaligned) && !(trb->ctrl &
Hi,
Thinh Nguyen writes:
>>> +static int dwc3_internal_states_show(struct seq_file *s, void *unused)
>>> +{
>>> + struct dwc3 *dwc = s->private;
>>> + unsigned intcurrent_mode;
>>> + unsigned long flags;
>>> + u32 reg;
>>> +
>>> + s
Hi John,
On 10/23/2018 5:43 PM, John Keeping wrote:
> By clearing the overrun flag as soon as the target frame is next
> incremented, we can end up incrementing the target frame more than
> expected in dwc2_gadget_handle_ep_disabled() when the endpoint's
> interval is greater than 1. This happens
In order to let host's parent device, rtsx_usb, to use USB remote wake
up signaling to do card detection, it needs to be suspended. Hence it's
necessary to add runtime PM support for the memstick host.
To keep memstick host stays suspended when it's not in use, convert the
card detection function
Use ms_dev() helper for consistency.
Signed-off-by: Kai-Heng Feng
---
drivers/memstick/host/rtsx_usb_ms.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/memstick/host/rtsx_usb_ms.c
b/drivers/memstick/host/rtsx_usb_ms.c
index e95e64974a91..24e9e6acf01a 100644
-
We can use MEMSTICK_POWER_{ON,OFF} along with pm_runtime_{get,put}
helpers to let memstick host support runtime pm.
The rpm count may go down to zero before the memstick host powers on, so
the host can be runtime suspended.
So before doing card detection, increment the rpm count to avoid the
host
If the probe fails, we should use pm_runtime_disable() to balance
pm_runtime_enable().
Add missing pm_runtime_disable() for rtsx_usb_ms.
Signed-off-by: Kai-Heng Feng
---
drivers/memstick/host/rtsx_usb_ms.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/memstick/host/rtsx_usb_ms.c
Although rtsx_usb doesn't support card removal detection, card insertion
will resume rtsx_usb by USB remote wakeup signaling.
When rtsx_usb gets resumed, also resumes its child devices,
rtsx_usb_sdmmc and rtsx_usb_ms, to notify them there's a card in its
slot.
Signed-off-by: Kai-Heng Feng
---
d
Hi,
This is based on Ulf's work [1] [2].
This patch series can keep rtsx_usb suspended, to save ~0.5W on Intel
platforms and ~1.5W on AMD platforms.
[1] https://patchwork.kernel.org/patch/10440583/
[2] https://patchwork.kernel.org/patch/10445725/
Kai-Heng Feng (5):
memstick: rtsx_usb_ms: Add
Replaced simple_strtoul with kstrtoul since simple_strtoul is obsolete.
Also fixed several formatting issues.
Signed-off-by: Ivan Roman
---
drivers/usb/serial/io_ti.c | 35 ---
1 file changed, 16 insertions(+), 19 deletions(-)
diff --git a/drivers/usb/serial/io_
On Wed 2018-08-22 22:42:58, Lubomir Rintel wrote:
> This will replace the ttc_usb_pdata.phy_{de,}init()>
">" -> "."?
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> arch/arm/mach-mmp/ttc_dkb.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/mach-mmp/ttc_dkb.c
On Wed 2018-08-22 22:42:55, Lubomir Rintel wrote:
> This is the PHY chip for USB OTG on PXA platforms.
>
> Signed-off-by: Lubomir Rintel
> ---
> .../devicetree/bindings/phy/phy-pxa-usb.txt | 17 +
> 1 file changed, 17 insertions(+)
> create mode 100644 Documentation/devicetr
On Wed 2018-08-22 22:43:02, Lubomir Rintel wrote:
> Use a proper PHY driver, instead of hooks to a board support package.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/pic
On Wed 2018-08-22 22:42:59, Lubomir Rintel wrote:
> This will replace the pxa168_sph_pdata.phy_{de,}init().
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
I'd merge this with the previous patch if it is easy. Your patches are
a bit too small...
On Wed 2018-08-22 22:43:06, Lubomir Rintel wrote:
> The USB OTG PHY chip. To be used by the OTG controller.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> arch/arm/boot/dts/mmp2.dtsi | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/mmp2.dtsi b/arc
On Wed 2018-08-22 22:43:03, Lubomir Rintel wrote:
> Use a proper PHY driver, instead of hooks to a board support package.
>
> Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
> ---
> arch/arm/mach-mmp/devices.c | 11 +---
> drivers/usb/gadget/udc/mv_udc.h | 7 -
> d
On Wed 2018-08-22 22:43:07, Lubomir Rintel wrote:
> Signed-off-by: Lubomir Rintel
> ---
> arch/arm/boot/dts/mmp2.dtsi | 11 +++
> 1 file changed, 11 insertions(+)
Again, I guess this could be merged with the previous patch. Anyway,
it is also good to go as-is.
Acked-by: Pavel Machek
>
Hi Ivan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.20-rc1 next-20181105]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Mon, Nov 05, 2018 at 12:50:09AM -0800, Ivan Roman wrote:
> Replaced simple_strtoul with kstrtoul since simple_strtoul is obsolete.
> Also fixed several formatting issues.
>
> Signed-off-by: Ivan Roman
> ---
> drivers/usb/serial/io_ti.c | 35 ---
> 1 file chang
On 26.10.2018 17:07, Alan Stern wrote:
On Fri, 26 Oct 2018, Dennis Wassenberg wrote:
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -2815,7 +2815,9 @@ static int hub_port_reset(struct usb_hub *hub, int port1,
USB_PORT_FEAT_C_BH_PORT_RESET);
Add the build system changes needed to get the Broadcom STB XHCI,
EHCI and OHCI functionality working. The link order for XHCI was
changed in the Makefile because of the way STB XHCI, EHCI and OHCI
controllers share a port which requires that the XHCI driver be
initialized first. Also update MAINTA
Add support for Broadcom STB SoC's to the ohci platform driver.
Signed-off-by: Al Cooper
---
drivers/usb/host/ohci-platform.c | 34 --
include/linux/usb/ohci_pdriver.h | 1 +
2 files changed, 29 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/host/ohci-pl
Add a new EHCI driver for Broadcom STB SoC's. A new EHCI driver
was created instead of adding support to the existing ehci platform
driver because of the code required to workaround bugs in the EHCI
controller.
Signed-off-by: Al Cooper
---
drivers/usb/host/ehci-brcm.c | 287 +
V3 - Based on feedback
- Patch 3/6
In xhci-brcm.h, fixed incorrect function name when
CONFIG_USB_XHCI_BRCM is not defined. Found by kbuild test robot.
- Patch 4/6
In ohci-platform.c, use devm_kmemdup() instead of demv_kzalloc().
- Patch 5/6
In ehci-platform.c, use dma_c
Add support for Broadcom STB SoC's to the xhci platform driver
Signed-off-by: Al Cooper
---
drivers/usb/host/xhci-brcm.c | 17 +
drivers/usb/host/xhci-brcm.h | 16
drivers/usb/host/xhci-plat.c | 8
3 files changed, 41 insertions(+)
create mode 100644 d
Add the ability to skip calling the PHY's exit routine on suspend
and the PHY's init routine on resume. This is to handle a USB PHY
that should have it's power_off function called on suspend but cannot
have it's exit function called because on exit it will disable the
PHY to the point where registe
Add DT bindings document for Broadcom STB USB OHCI, EHCI and
XHCI drivers.
Signed-off-by: Al Cooper
---
.../devicetree/bindings/usb/brcm,bcm7445-ehci.txt | 22 +
.../devicetree/bindings/usb/brcm,bcm7445-ohci.txt | 22 +
.../devicetree/bindings/usb/brcm,b
Hi Heikki, Rob,
Thanks for reviewing !
Should I update the patchset with the Reviewed-by tag and bumpup the
patchset version ?
Or is that not necessary?
Thanks,
Badhri.
On Fri, Nov 2, 2018 at 6:28 AM Heikki Krogerus
wrote:
>
> On Mon, Oct 01, 2018 at 12:45:01PM -0700, Badhri Jagan Sridharan wro
57 matches
Mail list logo
