Hi Baolu,
On 11 October 2016 at 12:32, Lu Baolu wrote:
> Hi,
>
> On 10/11/2016 12:07 PM, Baolin Wang wrote:
/*
>> + * usb_charger_unregister() - Unregister a usb charger.
>> + * @uchger - the usb charger to be unregistered.
>> + */
>> +static
Hi,
On 10/11/2016 12:07 PM, Baolin Wang wrote:
>>> /*
>>> >> + * usb_charger_unregister() - Unregister a usb charger.
>>> >> + * @uchger - the usb charger to be unregistered.
>>> >> + */
>>> >> +static int usb_charger_unregister(struct usb_charger *uchger)
>>> >> +{
>>> >> +
Hi Baolu,
On 11 October 2016 at 11:06, Lu Baolu wrote:
> Hi,
>
> On 10/10/2016 02:22 PM, Baolin Wang wrote:
>> When the usb gadget supporting for usb charger is ready, the usb charger
>> can implement the usb_charger_plug_by_gadget() function, usb_charger_exit()
>>
Hi Baolu,
On 11 October 2016 at 10:59, Lu Baolu wrote:
> Hi Baolin,
>
> Some review comments below.
>
> On 10/10/2016 02:22 PM, Baolin Wang wrote:
>> This patch introduces the usb charger driver based on usb gadget that
>> makes an enhancement to a power driver. It
On Mon, 2016-10-10 at 13:00 +0200, Matthias Brugger wrote:
>
> On 09/21/2016 07:54 AM, Chunfeng Yun wrote:
> > This patch adds support for the MediaTek USB3 controller
> > integrated into MT8173. It can be configured as Dual-Role
> > Device (DRD), Peripheral Only and Host Only (xHCI) modes.
> >
>
Hi,
On 10/10/2016 02:22 PM, Baolin Wang wrote:
> When the usb gadget supporting for usb charger is ready, the usb charger
> can implement the usb_charger_plug_by_gadget() function, usb_charger_exit()
> function and dev_to_uchger() function by getting 'struct usb_charger' from
> 'struct gadget'.
>
Hi Baolin,
Some review comments below.
On 10/10/2016 02:22 PM, Baolin Wang wrote:
> This patch introduces the usb charger driver based on usb gadget that
> makes an enhancement to a power driver. It works well in practice but
> that requires a system with suitable hardware.
>
> The basic
On Mon, 2016-10-10 at 12:55 +0200, Matthias Brugger wrote:
>
> On 09/21/2016 07:54 AM, Chunfeng Yun wrote:
> > Make IPPC register optional to support host side of dual-role mode,
> > due to it is moved into common glue layer for simplification.
> >
> > Signed-off-by: Chunfeng Yun
On 10/07/2016 11:42 AM, ahas...@baylibre.com wrote:
From: Axel Haslam
This patch documents the device tree bindings required for
the ohci controller found in TI da8xx family of SoC's
Signed-off-by: Axel Haslam
---
On 10/07/2016 11:42 AM, ahas...@baylibre.com wrote:
From: Axel Haslam
The usb20_phy clock needs to be registered for the driver to be able
to get and enable a clock. Currently the usb phy clocks are registered
form board files, which will not be called during a device
On 10/07/2016 11:42 AM, ahas...@baylibre.com wrote:
From: Axel Haslam
Currently requesting the vbus and overcurrent gpio is handled on
the board specific file. But this does not play well moving to
device tree.
In preparation to migrate to a device tree boot, handle
On Fri, Oct 07, 2016 at 06:42:54PM +0200, ahas...@baylibre.com wrote:
> From: Axel Haslam
>
> This patch documents the device tree bindings required for
> the ohci controller found in TI da8xx family of SoC's
>
> Signed-off-by: Axel Haslam
> ---
>
Hi guys!
Thanks for your efforts for fixing this bug! (The workaround of
loading the kernel with "usbcore.autosuspend=-1" works very fine for
me now).
Meanwhile, Asus gave me the expected response:
"Hello Mr. De Villemereuil,
Thank you for having solicited the ASUS Technical Support.
A
The Linux kernel supports many devices and each day more and more are
included, but there is a device that looks completely abandoned:
whiteboards. In my immediate environment a lot of interactive
whiteboards do not work under linux. Except some Smartboards, all
other lack support (Multiclass,
On 2016-10-08 23:07, Aidan Thornton wrote:
On Fri, Oct 7, 2016 at 12:30 PM, Johan Hovold wrote:
Why is this change needed? I see no write to this register in the
vendor driver.
In principle, it might not be because the value written to register
0x18 is probably overwritten
The Quectel EC21 and EC25 need the same "set DTR" request as devices
based on the MDM9230 chipset, but has no USB3 support. Our best guess
is that the "set DTR" functionality depends on chipset and/or
baseband firmware generation. But USB3 is still an optional feature.
Since we cannot enable this
On Wed 2016-08-31 14:23:13, Alan Stern wrote:
> On Tue, 30 Aug 2016, Rafał Miłecki wrote:
>
> > >> As you quite often need more complex LED management, there are
> > >> triggers that were introduced in 2006 by c3bc9956ec52f ("[PATCH] LED:
> > >> add LED trigger tupport"). Some triggers are
Hi!
> This commit adds a new trigger responsible for turning on LED when USB
> device gets connected to the specified USB port. This can can useful for
> various home routers that have USB port(s) and a proper LED telling user
> a device is connected.
>
> The trigger gets its documentation file
hi Alan/Krzysztof,
On 10 October 2016 at 02:47, Alan Stern wrote:
> On Sun, 9 Oct 2016, Krzysztof Kozlowski wrote:
>
>> On Sun, Oct 09, 2016 at 02:34:14PM +, Anand Moon wrote:
>> > Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP
>> > as to
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
On 09/21/2016 07:54 AM, Chunfeng Yun wrote:
Make IPPC register optional to support host side of dual-role mode,
due to it is moved into common glue layer for simplification.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 36
On 10/10/16 12:26, Felipe Balbi wrote:
>
> Hi,
>
> Juergen Gross writes:
>
>> Signed-off-by: Juergen Gross
>
> I can't apply anything without a commit log. Sorry.
I always thought a subject line telling the complete story would be
enough. I'll resend with
Use kasprintf() instead of open coding it.
Signed-off-by: Juergen Gross
---
drivers/usb/gadget/composite.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
index 32176f7..455efec
Hi,
Juergen Gross writes:
> Signed-off-by: Juergen Gross
I can't apply anything without a commit log. Sorry.
> diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
> index 32176f7..455efec 100644
> ---
Signed-off-by: Juergen Gross
---
drivers/usb/gadget/composite.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
index 32176f7..455efec 100644
--- a/drivers/usb/gadget/composite.c
On Fri, Oct 7, 2016 at 5:31 PM, Martyn Welch
wrote:
> WRT this driver, I think I need to keep set_single_ended, but change
> .direction_input
> to always return a failure and have .direction_output always return success to
> avoid pins being driven in unexpected
Ping.
> -Original Message-
>
> I am trying to investigate an issue on a TI Sitara CPU, AM3352 with the musb
> USB controller.
>
> The scenario is that a device has been in use and working correctly. The
> device is an Android device and is presenting as an MTP device. That first
>
On Sun, 9 Oct 2016, Steinar H. Gunderson wrote:
> The Akai MIDImix (09e8:0031) is a MIDI fader controller that speaks
> regular MIDI and works well with Linux. However, initialization gets
> delayed due to reports timeout:
>
> [3643645.631124] hid-generic 0003:09E8:0031.0020: timeout
On Mon, 3 Oct 2016, Heiner Kallweit wrote:
> The hid-led driver works fine under 4.8.0, however with the next
> kernel from today I get this:
Queued in hid.git for 4.9-rc. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a
On Fri, 2016-10-07 at 22:26 +0100, Snaper wrote:
> Hi,
>
> This is on a BeagleBoard-xM with a fresh image from
> https://eewiki.net/display/linuxonarm/BeagleBoard.
>
> I attach the output of dmesg after booting.
>
> Some seconds after booting USB seems to crash, since the keyboard no
> longer
When we change the USB function with configfs frequently, sometimes it will
hang the system to crash. The reason is the gadget driver can not hanle the
end transfer complete event after free the gadget irq (since the xHCI will
share the same interrupt number with gadget, thus when free the gadget
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
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 can do the power things.
Signed-off-by: Baolin Wang
When the usb gadget supporting for usb charger is ready, the usb charger
can implement the usb_charger_plug_by_gadget() function, usb_charger_exit()
function and dev_to_uchger() function by getting 'struct usb_charger' from
'struct gadget'.
Signed-off-by: Baolin Wang
36 matches
Mail list logo