On Wed, 2019-06-05 at 17:02 -0400, Alan Stern wrote:
> On Wed, 5 Jun 2019, Greg KH wrote:
>
> >
> > On Fri, May 10, 2019 at 11:01:09AM +0100, Mayuresh Kulkarni wrote:
> > >
> > > - The current driver increments the PM ref-count in its .open
> > > API and decrements it in its .close API.
> > > -
From: Hans Ulli Kroll
Add device tree probing to the fotg2 driver.
Signed-off-by: Hans Ulli Kroll
[Drop DMA mask coercion, drivers/of/platform.c does the job]
Signed-off-by: Linus Walleij
---
drivers/usb/host/fotg210-hcd.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/driver
Prolific has developed a new USB to UART chip: PL2303HXN
PL2303HXN : PL2303GC/PL2303GS/PL2303GT/PL2303GL/PL2303GE/PL2303GB
The Vendor request used by the PL2303HXN (TYPE_HXN) is different from
the existing PL2303 series (TYPE_HX & TYPE_01).
Therefore, different Vendor requests are used to issue rel
On Wed, 2019-06-05 at 11:41 +0200, Greg KH wrote:
> On Fri, May 10, 2019 at 11:01:09AM +0100, Mayuresh Kulkarni wrote:
> >
> > - The current driver increments the PM ref-count in its .open
> > API and decrements it in its .close API.
> > - Due to this, it is not possible for the usb_device to go i
On Thu, Jun 13, 2019 at 03:33:02PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Greg KH writes:
> >> > > > Who can use this interface in the "real world", is it only
> >> > > > developers that have access to the special hardware dongle? Or can
> >> > > > anyone use this on their laptops for getting c
Hi,
Greg KH writes:
>> > > > Who can use this interface in the "real world", is it only
>> > > > developers that have access to the special hardware dongle? Or can
>> > > > anyone use this on their laptops for getting console access in a way
>> > > > that is somehow "better" than the existing i
Clang produces the following warning
drivers/usb/host/xhci-tegra.c:357:27: warning: unused variable
'mbox_cmd_name' [-Wunused-const-variable]
static const char * const mbox_cmd_name[] = {
Looks like it was intended for logging or debugging, but was
never implemented. Removing mbox_cmd_name.
Cc:
On Thu, 13 Jun 2019, Mayuresh Kulkarni wrote:
> Hi Alan,
>
> Thanks for your review and apologies for late response from me. I was on PTO
> last week and then in a training this week.
>
> > Aside from the issues Greg raised, it isn't right because it relies onĀ
> > the suspend and resume callba
On Thu, May 16, 2019 at 12:09:28PM +0530, Nagarjuna Kristam wrote:
> Add device-tree binding documentation for the XUSB device mode controller
> present on Tegra210 SoC. This controller supports the USB 3.0
> specification.
>
> Signed-off-by: Nagarjuna Kristam
> ---
> .../devicetree/bindings/usb
Hi Johan,
Thanks for the info. I followed
https://nickdesaulniers.github.io/blog/2017/05/16/submitting-your-first-patc
h-to-the-linux-kernel-and-responding-to-feedback/ and made a proposal patch
("[PATCH] USB: serial: ch341: fix wrong baud rate setting calculation"). The
Get_maintainers.pl file di
On 11-06-2019 13:13, Chunfeng Yun wrote:
> On Mon, 2019-06-10 at 15:49 +0530, Nagarjuna Kristam wrote:
>> Add device-tree binding documentation for the XUSB device mode controller
>> present on Tegra210 SoC. This controller supports the USB 3.0
>> specification.
>>
>> Signed-off-by: Nagarjuna Kr
On Sat, Jun 08, 2019 at 05:49:51PM +1200, Jonathan Olds wrote:
> Hi Johan,
>
> Thanks for the info. I followed
> https://nickdesaulniers.github.io/blog/2017/05/16/submitting-your-first-patc
> h-to-the-linux-kernel-and-responding-to-feedback/ and made a proposal patch
> ("[PATCH] USB: serial: ch341
12 matches
Mail list logo