On 14 August 2015 at 16:55, Li Jun b47...@freescale.com wrote:
Hi Baolin,
On Fri, Aug 14, 2015 at 05:47:43PM +0800, Baolin Wang wrote:
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
On Fri, Aug 14, 2015 at 10:18:39AM +0800, Peter Chen wrote:
The following changes since commit e6bbe1d05353a29628a4ca72d88bac0bdcec5f38:
Merge 4.2-rc6 into usb-next (2015-08-10 10:01:33 -0700)
are available in the git repository at:
Hello Suravee,
On 08/13/2015 08:45 PM, Suravee Suthikulpanit wrote:
On 8/13/15 04:51, Jeremy Linton wrote:
ACPI configurations can now mark devices as noncoherent,
support that choice.
This change was in my earlier revisions for the original patch series to
add ACPI CCA support. At the time,
ping...
More than a week has passed, haven't seen any response though. Any comments?
On 05-08-15 08:54, Mike Looijmans wrote:
USB network adapters support Jumbo frames. The only thing blocking
that feature is the code in the gadget driver that disposes of
packets larger than 1518 bytes, and
On Thu 13-08-15 09:01:28, Darrick J. Wong wrote:
On Wed, Aug 12, 2015 at 08:17:28PM -0700, Duc Dang wrote:
Hi Theodore, Andreas, Jan, Andrew and All,
We are seeing kernel trace when we disconnect an USB/SATA/MMC devices
that has its ext2/ext3/ext4 partition currently mounted. These
Am Freitag, den 07.08.2015, 15:15 +0800 schrieb Peter Chen:
It is used to override the default setting for burst size, changing
burst size takes effect only when the SBUSCFG.AHBBRST = 0.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
On Thu, Aug 13, 2015 at 11:01:18AM -0400, Alan Stern wrote:
On Thu, 13 Aug 2015, Peter Chen wrote:
Alan, do you have any suggestions? Currently, IP core driver and ehci
core both takes its internal structure as driver data. Thanks.
It's not just ehci-hcd: The USB core stores the
On Fri, Aug 14, 2015 at 10:26:35AM -0400, Alan Stern wrote:
On Fri, 14 Aug 2015, Peter Chen wrote:
In the old days, a single device could be a USB host controller and
nothing else. Then later, a single device could be either a host
controller or a device controller. Now a single
On Fri, 14 Aug 2015, Peter Chen wrote:
In the old days, a single device could be a USB host controller and
nothing else. Then later, a single device could be either a host
controller or a device controller. Now a single device can be both.
Obviously this causes problems for our
On Fri, 14 Aug 2015, Felipe Balbi wrote:
That's not quite what I had in mind. I was thinking of something more
like this:
Platform device drvdata struct usb_pointers
|
|
|---|---|
|
On Fri, Aug 14, 2015 at 05:47:45PM +0800, 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 conception of the usb charger is
On 8/13/2015 8:29 PM, Yunzhi Li wrote:
在 2015/8/14 8:09, John Youn 写道:
On 8/11/2015 12:57 AM, Yunzhi Li wrote:
We initiate dwc2 usb controller in BIOS, when kernel driver
start-up we should reset AHB hclk domain to reset all AHB
interface registers to default. Without this the FIFO value
Hi,
21.07.2015 17:22, Oliver Neukum пишет:
On Mon, 2015-07-20 at 21:13 +0300, Eugene Shatokhin wrote:
And here, the code clears EVENT_RX_KILL bit in dev-flags, which may
execute concurrently with the above operation:
#0 clear_bit (bitops.h:113, inlined)
#1 usbnet_bh (usbnet.c:1475)
/*
Both races may happen when a device (e.g. YOTA 4G LTE Modem) is
unplugged while the system is downloading a large file from the Net.
Hardware breakpoints and Kprobes with delays were used to confirm that
the races do actually happen.
1. The first race is on skb_queue ('next' pointer) between
On Wednesday 12 August 2015 16:51:29 Jeremy Linton wrote:
diff --git a/drivers/usb/host/ehci-platform.c
b/drivers/usb/host/ehci-platform.c
index 2593def..82e396f 100644
--- a/drivers/usb/host/ehci-platform.c
+++ b/drivers/usb/host/ehci-platform.c
@@ -162,8 +162,10 @@ static int
On Thu, Aug 13, 2015 at 09:26:50AM -0500, Felipe Balbi wrote:
Hi Greg,
here's the big Gadget pull request. It contains 146 non-merge commits this
time around.
All patches have been soaking in next for quite a while and have also been
tested with the platforms I have around.
Let me know
Arnd,
On 08/14/2015 04:19 PM, Arnd Bergmann wrote:
On Wednesday 12 August 2015 16:51:29 Jeremy Linton wrote:
diff --git a/drivers/usb/host/ehci-platform.c b/drivers/usb/host/ehci-platform.c
index 2593def..82e396f 100644
--- a/drivers/usb/host/ehci-platform.c
+++
On Friday 14 August 2015 16:44:12 Jeremy Linton wrote:
On 08/14/2015 04:19 PM, Arnd Bergmann wrote:
On Wednesday 12 August 2015 16:51:29 Jeremy Linton wrote:
diff --git a/drivers/usb/host/ehci-platform.c
b/drivers/usb/host/ehci-platform.c
index 2593def..82e396f 100644
---
On Mon, Aug 10, 2015 at 11:05:11AM +, AMAN DEEP wrote:
There is a race condition between
finish_unlinks-finish_urb() function and
usb_kill_urb() in ohci controller case. The finish_urb
calls spin_unlock(ohci-lock) before
usb_hcd_giveback_urb() function call, then if during
this
On Tue, Aug 11, 2015 at 04:10:47PM +0100, Joao Pinto wrote:
Hi!
When testing our USB 3.0 Device IP solution we typically run the Compliance
Tests for USB 3.0 and also for USB 2.0. We find an issue regarding the USB 2.0
CV Chapter 9 test: LPM L1 Suspend Resume Test.
For it to be successful
On Tue, Aug 11, 2015 at 03:24:04PM -0400, Abhilash Jindal wrote:
Wall time obtained from do_gettimeofday is susceptible to sudden jumps due to
user setting the time or due to NTP. Boot time is constantly increasing time
better suited for comparing two timestamps.
Signed-off-by: Abhilash
On Fri, Aug 14, 2015 at 10:18:39AM +0800, Peter Chen wrote:
The following changes since commit e6bbe1d05353a29628a4ca72d88bac0bdcec5f38:
Merge 4.2-rc6 into usb-next (2015-08-10 10:01:33 -0700)
are available in the git repository at:
On Fri, Aug 14, 2015 at 1:09 AM, Jan Kara j...@suse.cz wrote:
On Thu 13-08-15 09:01:28, Darrick J. Wong wrote:
On Wed, Aug 12, 2015 at 08:17:28PM -0700, Duc Dang wrote:
Hi Theodore, Andreas, Jan, Andrew and All,
We are seeing kernel trace when we disconnect an USB/SATA/MMC devices
that
tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
head: 17248569499eae54b314fb05c4ff19fd47c9e99b
commit: 484ebaedecc5ddf778a30ee1efab367cbee27030 [49/60] usb: interface
authorization: Declare authorized attribute
reproduce: make htmldocs
All warnings (new ones
Removed some checkpatch.pl warnings saying there was an unwanted space between
function names and their arguments.
Signed-off-by: Chase Metzger chasemetzge...@gmail.com
---
drivers/usb/core/hub.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
On 2015-08-15 11:41, Chase Metzger wrote:
Removed some checkpatch.pl warnings saying there was an unwanted space between
function names and their arguments.
Signed-off-by: Chase Metzger chasemetzge...@gmail.com
---
drivers/usb/core/hub.c | 16
1 file changed, 8
On Fri, 14 Aug 2015, Baolin Wang wrote:
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
Hi Peter,
On 13/07/15 13:20, Roger Quadros wrote:
On 13/07/15 05:14, Peter Chen wrote:
On Wed, Jul 08, 2015 at 01:19:33PM +0300, Roger Quadros wrote:
The OTG core instantiates the OTG Finite State Machine
per OTG controller and manages starting/stopping the
host and gadget controllers based
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
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
The usb charger framework is based on usb gadget, and each usb gadget
can be one usb charger to set the current limitation.
This patch adds a notifier mechanism for usb charger to report to usb
charger when the usb gadget state is changed.
Also we introduce a callback 'get_charger_type' which
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.
On 14 August 2015 at 02:11, Krzysztof Opasiak k.opas...@samsung.com wrote:
On 08/13/2015 09:57 PM, Greg Kroah-Hartman wrote:
On Thu, Aug 13, 2015 at 09:34:46PM +0200, Krzysztof Opasiak wrote:
Hello,
On 08/13/2015 09:12 PM, Amit Pundir wrote:
his MTP function is based on years of work
Hi Baolin,
On Fri, Aug 14, 2015 at 05:47:43PM +0800, Baolin Wang wrote:
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
On Fri, Aug 14, 2015 at 10:37:30AM +0200, Lucas Stach wrote:
Am Freitag, den 07.08.2015, 15:15 +0800 schrieb Peter Chen:
It is used to override the default setting for burst size, changing
burst size takes effect only when the SBUSCFG.AHBBRST = 0.
Signed-off-by: Peter Chen
On Fri, Aug 14, 2015 at 12:42:38PM +0300, Roger Quadros wrote:
Hi Peter,
On 13/07/15 13:20, Roger Quadros wrote:
On 13/07/15 05:14, Peter Chen wrote:
On Wed, Jul 08, 2015 at 01:19:33PM +0300, Roger Quadros wrote:
The OTG core instantiates the OTG Finite State Machine
per OTG controller
Am Freitag, den 14.08.2015, 16:40 +0800 schrieb Peter Chen:
On Fri, Aug 14, 2015 at 10:37:30AM +0200, Lucas Stach wrote:
Am Freitag, den 07.08.2015, 15:15 +0800 schrieb Peter Chen:
It is used to override the default setting for burst size, changing
burst size takes effect only when the
On Fri, Aug 14, 2015 at 08:45:22AM +0700, Suravee Suthikulpanit wrote:
On 8/13/15 04:51, Jeremy Linton wrote:
ACPI configurations can now mark devices as noncoherent,
support that choice.
Signed-off-by: Jeremy Linton jeremy.lin...@arm.com
---
include/acpi/acpi_bus.h | 5 +++--
1 file
38 matches
Mail list logo
