GFP_KERNEL used when a lock is held. Convert to GFP_ATOMIC to avoid
the possibility of deadlock.
Fixes: 725d53536473 ("usb: xhci: Add DbC support in xHCI driver")
Signed-off-by: Julia Lawall
Signed-off-by: Fengguang Wu
---
I don't have access to any more of the context than what is shown so I
In the SG case this is already handled since a non-zero
request->num_mapped_sgs is a clear indicator that dma_map_sg()
had been called. While it would be nice to do the same for the
singly mapped case by simply checking for non-zero request->dma,
it's conceivable that 0 is a valid dma_addr_t handle
On Tue, Aug 01, 2017 at 08:49:02AM +0200, Linus Walleij wrote:
> On Thu, Jul 6, 2017 at 10:49 PM, Anatolij Gustschin wrote:
>
> > Add driver for CBUS pins on FT232H. The driver supports setting
> > GPIO direction and getting/setting CBUS 0-3 pin value. The CBUS
> > pins have to be enabled by conf
Hi Jack-san,
> -Original Message-
> From: Jack Pham
> Sent: Tuesday, August 1, 2017 6:01 PM
> Subject: [PATCH] usb: gadget: core: unmap request from DMA only if previously
> mapped
>
> In the SG case this is already handled since a non-zero
> request->num_mapped_sgs is a clear indicator
Some buggy USB disk adapters disconnect and reconnect multiple times
during the enumeration procedure. This may lead to a device
connecting at full speed instead of high speed, because when the USB
stack sees that a device isn't able to enumerate at high speed, it
tries to hand the connection over
Cc: sta...@vger.kernel.org
Signed-off-by: Hector Martin
---
drivers/usb/serial/option.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index ebe51f11105d..fe123153b1a5 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/seria
Cc: sta...@vger.kernel.org
Signed-off-by: Hector Martin
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index 5894e3c9468f..ff6f39fe6c00 100644
--- a/drivers/net/usb/qmi_wwan.c
+++ b/drivers/net/usb/qmi_wwa
I'm running archlinux on a Dell XPS15 9550 and I connect it to a TB16
thunderbolt dock. Connected to the dock I have a 4k external display and
a USB logitech transmitter for my wireless keyboard and mouse.
The TB16 dock is a finicky beast and doesn't currently work 100% with
linux. However, if
On Wed, Aug 02, 2017 at 12:45:06AM +0900, Hector Martin wrote:
I'll fix it up this time, but please make sure to include a proper
commit message in the future.
> Cc: sta...@vger.kernel.org
> Signed-off-by: Hector Martin
Now applied, thanks.
Johan
--
To unsubscribe from this list: send the line
Felipe,
I've found a problem in the gadget serial driver, which I believe is
triggered in the following scenario:
1) Both host and gadget system have a USB gadget serial port open.
2) Gadget side application closes the serial port.
3) Host side sends data to the serial port.
(Steps 2, 3 may
On Thu, Jul 13, 2017 at 10:26:40AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 12, 2017 at 10:12:34PM -0500, Bjorn Helgaas wrote:
> > On Mon, Jul 10, 2017 at 04:52:28PM +0100, Marc Zyngier wrote:
> > > Ard and myself have just spent quite some time lately trying to pin
> > > down an issue in the
On 1 August 2017 at 22:44, Bjorn Helgaas wrote:
> On Thu, Jul 13, 2017 at 10:26:40AM +0200, Greg Kroah-Hartman wrote:
>> On Wed, Jul 12, 2017 at 10:12:34PM -0500, Bjorn Helgaas wrote:
>> > On Mon, Jul 10, 2017 at 04:52:28PM +0100, Marc Zyngier wrote:
>> > > Ard and myself have just spent quite som
On Mon, Jul 10, 2017 at 04:52:28PM +0100, Marc Zyngier wrote:
> Ard and myself have just spent quite some time lately trying to pin
> down an issue in the DMA code which was taking the form of a PCIe USB3
> controller issuing a DMA access at some bizarre address, and being
> caught red-handed by th
On 08/01/2017 07:41 AM, Alan Stern wrote:
Some buggy USB disk adapters disconnect and reconnect multiple times
during the enumeration procedure. This may lead to a device
connecting at full speed instead of high speed, because when the USB
stack sees that a device isn't able to enumerate at high
The latest HW manual (Rev.0.55) shows us this UGCTRL2.VBUSSEL bit.
If the bit sets to 1, the VBUS drive is controlled by phy related
registers (called "UCOM Registers" on the manual). Since R-Car Gen3
environment will control VBUS by phy-rcar-gen3-usb2 driver,
the UGCTRL2.VBUSSEL bit should be set
Vivek,
On Monday 31 July 2017 10:58 AM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Tue, Jun 20, 2017 at 11:27 AM, Vivek Gautam
> wrote:
>> Fixing the clk enable failure path in qcom_qmp_phy_init()
>> and cleanup the reset control deassertion failure path in
>> qcom_qmp_phy_com_init().
>>
>> Fixe
On Monday 17 July 2017 06:50 AM, Chanwoo Choi wrote:
> This patch uses the resource-managed extcon API for extcon_register_notifier()
> and replaces the deprecated extcon API as following:
> - extcon_get_cable_state_() -> extcon_get_state()
> - extcon_set_cable_state_() -> extcon_set_state_sync()
On Monday 17 July 2017 06:50 AM, Chanwoo Choi wrote:
> This patch replaces the deprecated extcon API as following:
> - extcon_set_cable_state_() -> extcon_get_state()
>
> Cc: Kishon Vijay Abraham I
> Cc: Raviteja Garimella
> Signed-off-by: Chanwoo Choi
Acked-by: Kishon Vijay Abraham I
> ---
On Wed, Aug 2, 2017 at 10:39 AM, Kishon Vijay Abraham I wrote:
> Vivek,
>
> On Monday 31 July 2017 10:58 AM, Vivek Gautam wrote:
>> Hi Kishon,
>>
>>
>> On Tue, Jun 20, 2017 at 11:27 AM, Vivek Gautam
>> wrote:
>>> Fixing the clk enable failure path in qcom_qmp_phy_init()
>>> and cleanup the reset
19 matches
Mail list logo
