For OUT endpoints, zero-length transfers require MaxPacketSize buffer as
per the DWC_usb3 programming guide 3.30a section 4.2.3.3.
This patch fixes this by explicitly checking zero length
transfer to correctly pad up to MaxPacketSize.
Fixes: c6267a51639b ("usb: dwc3: gadget: align transfers to wM
> Am 17.01.19 um 08:01 schrieb Peter Chen:
> >
> >>
> >> The i.MX6q/dl USB controller may drive the usb power line directly,
> >> but the polarity depends on the board. Reset state of the polarity is
> >> low-active so add this property to allow it to be high-active.
> >>
> >
> > As far as I know
Hi,
Thinh Nguyen writes:
> Try to dequeue a request that was already completed. Odd. Why are we
> missing a call to giveback??
Got a little more information:
file-storage-3982 [006] d... 131.010663: dwc3_ep_queue: ep1in: req
eccaa10f length 0/16384 zsI
Hi Heikki,
Heikki Krogerus 于2018年10月24日周三 下午11:06写道：
>
> When the connections are defined in firmware, struct
> device_connection will have the fwnode member pointing to
> the device node (struct fwnode_handle) of the requested
> device, and the endpoint will not be used at all in that
> case.
>
>
Hi,
On 1/21/2019 9:47 PM, Sergei Shtylyov wrote:
> Hello!
>
> On 01/21/2019 12:33 PM, Tejas Joglekar wrote:
>
>> For OUT endpoints, zero-length transfers require MaxPacketSize buffer as
>> per the DWC_usb3 programming guide 3.30a section 4.2.3.3.
>>
>> This patch fixes this by explicitly checking z
Hi Rob,
On January 22, 2019 09:03, Rob Herring wrote:
>
> On Wed, Jan 16, 2019 at 06:48:06AM +, Ran Wang wrote:
> > When DWC3 is set to host mode by programming register DWC3_GCTL,
> VUBS
>
> s/VUBS/VBUS/
Yes, will fix it in next version.
> > (or its control signal) will on immediately on
Hi Felipe,
On 1/21/2019 4:15 AM, Felipe Balbi wrote:
> Hi
>
> Felipe Balbi writes:
>> Hi,
>>
>> Felipe Balbi writes:
>>> Hi again,
>>>
>>> Felipe Balbi writes:
>>>
>>>
>>>
Try to dequeue a request that was already completed. Odd. Why are we
missing a call to giveback??
>>> Got a litt
Hi Bin,
On Mon, 2019-01-21 at 10:07 -0600, Bin Liu wrote:
> Hi Min,
>
> On Mon, Jan 21, 2019 at 08:22:31PM +0800, min@mediatek.com wrote:
> > From: Min Guo
> >
> > This adds support for MediaTek musb controller in
> > host, peripheral and otg mode.
> > There are some quirk of MediaTek musb
Hi Bin,
On Mon, 2019-01-21 at 09:59 -0600, Bin Liu wrote:
> Hi Min,
>
> On Mon, Jan 21, 2019 at 08:22:30PM +0800, min@mediatek.com wrote:
> > From: Min Guo
> >
> > Delete the const attribute of addr parameter in readb/w/l hooks, these
> > changes are for implementing clearing W1C registers.
On Wed, Jan 16, 2019 at 10:57:40AM +0100, Nicolas Ferre wrote:
> This removes a line left while adding the correct compatibility string for
> sama5d3 10/100 interface. Now use the "atmel,sama5d3-macb" string.
>
> Signed-off-by: Nicolas Ferre
> ---
> Documentation/devicetree/bindings/net/macb.txt
On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
> Update the Reset Controller's binding to add new SoC compatibility string.
>
> Signed-off-by: Nicolas Ferre
> ---
> Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/D
On Wed, 16 Jan 2019 10:57:37 +0100, Nicolas Ferre wrote:
> Add this missing compatibility string to the Reset Controller
> compatible string chip list.
>
> Signed-off-by: Nicolas Ferre
> ---
> Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 del
On Wed, Jan 16, 2019 at 06:48:06AM +, Ran Wang wrote:
> When DWC3 is set to host mode by programming register DWC3_GCTL, VUBS
s/VUBS/VBUS/
> (or its control signal) will on immediately on related Root Hub ports.
/will on/will turn on/
> Then the VUBS will be de-asserted for a little while d
Add nodes for USB and related PHYs.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 22
arch/arm64/boot/dts/qcom/msm8998.dtsi | 92 +++
2 files changed, 114 insertions(+)
diff --git a/arch/arm64/b
Add a MSM8998 specific DT compatible so that we can properly bind to the
device and enable the USB controller.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
---
drivers/usb/dwc3/dwc3-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb
msm8998 USB has a dwc3 controller just like the existing sdm845 support.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
---
Documentation/devicetree/bindings/usb/qcom,dwc3.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.txt
b/Do
This series provides basic USB support for MSM8998. Currently missing is
wiring up the Type-C detection logic so that the controller can correctly
switch between host and peripheral modes. Work to implement that is
ongoing, and expected to appear soon in followup patches. Also missing is
Display
If clk_prepare_enable() fails in dwc3_exynos_probe() or in
dwc3_exynos_resume(), exynos->clks[0] is left undisabled
because of usage preincrement in while condition.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
Fixes: 9f2168367a0a ("usb: dwc3:
Bin Liu writes:
> On Fri, Jan 18, 2019 at 08:15:02PM +, Måns Rullgård wrote:
>> Bin Liu writes:
>>
>> > On Mon, Dec 17, 2018 at 09:36:17PM +, Måns Rullgård wrote:
>> >> Bin Liu writes:
>> >>
>> >> > On Mon, Dec 17, 2018 at 07:16:08PM +, Måns Rullgård wrote:
>> >> >> Bin Liu write
Dearest One
First i thanks your attention to me, I am mercy kings My parents
Mr.and Mrs.kings were assassinated here in IVORY COAST. Before my
Before my father's death he had (USD $5.9M) Five Million Nine Hundred
Thousand United State Dollars deposited in a bank here in Abidjan. I
want you to do m
Hi!
Am 16.01.19 um 17:32 schrieb Sergei Shtylyov:
> Hello!
>
> On 01/16/2019 01:51 PM, Philipp Puschmann wrote:
>
>> This patch adds support to set the power line polarity for i.MX6q/dl.
>>
>> To let the USB controller control the power it may be necessary to configure
>> the polarity of the pow
Hi Peter,
Am 17.01.19 um 08:01 schrieb Peter Chen:
>
>>
>> The i.MX6q/dl USB controller may drive the usb power line directly, but the
>> polarity
>> depends on the board. Reset state of the polarity is low-active so add this
>> property
>> to allow it to be high-active.
>>
>
> As far as I kn
On Mon, Jan 21, 2019 at 10:04:06AM +0200, Mike Rapoport wrote:
> Add check for the return value of memblock_alloc*() functions and call
> panic() in case of error.
> The panic message repeats the one used by panicing memblock allocators with
> adjustment of parameters to include only relevant ones.
On Fri, Jan 18, 2019 at 08:15:02PM +, Måns Rullgård wrote:
> Bin Liu writes:
>
> > On Mon, Dec 17, 2018 at 09:36:17PM +, Måns Rullgård wrote:
> >> Bin Liu writes:
> >>
> >> > On Mon, Dec 17, 2018 at 07:16:08PM +, Måns Rullgård wrote:
> >> >> Bin Liu writes:
> >> >>
> >> >> > Hi,
>
Hello!
On 01/21/2019 12:33 PM, Tejas Joglekar wrote:
> For OUT endpoints, zero-length transfers require MaxPacketSize buffer as
> per the DWC_usb3 programming guide 3.30a section 4.2.3.3.
>
> This patch fixes this by explicitly checking zero length
> transfer to correctly pad up to MaxPacketSize
Hi Min,
On Mon, Jan 21, 2019 at 08:22:31PM +0800, min@mediatek.com wrote:
> From: Min Guo
>
> This adds support for MediaTek musb controller in
> host, peripheral and otg mode.
> There are some quirk of MediaTek musb controller, such as:
> -W1C interrupt status registers
> -Private data to
Hi Min,
On Mon, Jan 21, 2019 at 08:22:30PM +0800, min@mediatek.com wrote:
> From: Min Guo
>
> Delete the const attribute of addr parameter in readb/w/l hooks, these
> changes are for implementing clearing W1C registers.
> Replace musb_readb/w with musb_clearb/w to clear the interrupt status.
Hi Rob,
On lun., janv. 21 2019, Rob Herring wrote:
> On Mon, 21 Jan 2019 12:23:32 +0100, Miquel Raynal wrote:
>> Add bindings for Marvell Armada 3700 USB2 UTMI+ PHY.
>>
>> Signed-off-by: Miquel Raynal
>> ---
>> .../bindings/phy/phy-mvebu-utmi.txt | 38 +++
>> 1 fil
On Mon, 21 Jan 2019 12:23:32 +0100, Miquel Raynal wrote:
> Add bindings for Marvell Armada 3700 USB2 UTMI+ PHY.
>
> Signed-off-by: Miquel Raynal
> ---
> .../bindings/phy/phy-mvebu-utmi.txt | 38 +++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/
On Thu, Jan 17, 2019 at 07:33:27PM -0300, Paul Cercueil wrote:
> This commit adds documentation for the device-tree bindings of the
> jz4740-musb driver, which provides support for the USB gadget mode
> of the JZ4740 and similar SoCs from Ingenic.
>
> Signed-off-by: Paul Cercueil
> Reviewed-by: R
On Mon, Jan 21, 2019 at 08:22:26PM +0800, min@mediatek.com wrote:
> From: Min Guo
>
> This adds support for MediaTek musb controller in
> host, peripheral and otg mode.
>
> Signed-off-by: Min Guo
> ---
> changes in v4:
> suggested by Sergei:
> 1. String alignment
>
> changes in v3:
> 1. no
Note that it only works with USB_XHCI_PLATFORM=y. Also it needs a hard
reset when coming from an unpatched kernel.
This was included in the original patch in
https://patchwork.kernel.org/patch/9992809/ but got dropped when
accepted in d8c80bb3b55b phy: exynos5-usbdrd: Calibrate LOS levels for
exy
On Mon, Jan 21, 2019 at 11:30:55PM +0900, Suwan Kim wrote:
> usb_create_ep_devs() returns error code if an error occurs. But
> usb_new_device() and create_intf_ep_devs() which use usb_create_ep_devs()
> to create endpoint devices ignore the error and cut the propagation
> of the error when usb_crea
USB3503 chip can be used without any I2C connection, what is handled by
a simple platform device driver. Add support for resetting the chip (via
GPIO lines) during system suspend/resume cycle by adding calls to existing
suspend/resume functions used for E2C device.
Signed-off-by: Marek Szyprowski
usb_create_ep_devs() returns error code if an error occurs. But
usb_new_device() and create_intf_ep_devs() which use usb_create_ep_devs()
to create endpoint devices ignore the error and cut the propagation
of the error when usb_create_ep_devs() fails. So, usb_create_ep_devs()
prints an error messag
Hi,
On Mon, Jan 21, 2019 at 04:36:13PM +0800, Chen Yu wrote:
> Have the fwnode_get_name() patches been accepted?
No, I didn't have a user for the function anymore:
https://lkml.org/lkml/2018/12/17/284
> And I will be grateful if you can tell me your plan about the
> https://lkml.org/lkml/2018/10
From: Andrzej Pietrasiewicz
This patch adds support for transferring requests, which are
non-contiguous in physical memory, i.e. the data buffer is described by
a scatter-list. This allows transferring large requests without relying
on error-prone contiguous buffer allocations. This way of alloca
From: Min Guo
Delete the const attribute of addr parameter in readb/w/l hooks, these
changes are for implementing clearing W1C registers.
Replace musb_readb/w with musb_clearb/w to clear the interrupt status.
Signed-off-by: Min Guo
---
new patch based on v3:
---
drivers/usb/musb/musb_core.c |
From: Min Guo
Add get/set toggle hooks in struct musb_io and struct musb_platform_ops
for special platform; remove function musb_save_toggle, use the set/get
callback to handle toggle.
Signed-off-by: Min Guo
---
new patch based on v3:
---
drivers/usb/musb/musb_core.c | 42 +
From: Min Guo
Add noirq type of dma create interface for platform which do not
have dedicated DMA interrupt line, move musbhsdma macro definition
to musb_dma.h
Signed-off-by: Min Guo
---
new patch based on v3:
---
drivers/usb/musb/musb_dma.h | 9
drivers/usb/musb/musbhsdma.c | 54 ++
From: Min Guo
These patches introduce the MediaTek MUSB controller driver.
The driver can be configured as Dual-Role Device (DRD),
Peripheral Only and Host Only modes. This has beed tested on
MT2701 with a variety of devices in host mode and with the
f_mass gadget driver in peripheral mode, plu
From: Min Guo
This adds support for MediaTek musb controller in
host, peripheral and otg mode.
Signed-off-by: Min Guo
---
changes in v4:
suggested by Sergei:
1. String alignment
changes in v3:
1. no changes
changes in v2:
suggested by Bin:
1. Modify DRC to DRD
suggested by Rob:
2. Drop the "-
From: Min Guo
This adds support for MediaTek musb controller in
host, peripheral and otg mode.
There are some quirk of MediaTek musb controller, such as:
-W1C interrupt status registers
-Private data toggle registers
-No dedicated DMA interrupt line
Signed-off-by: Min Guo
Signed-off-by: Yong
From: Min Guo
Add musb nodes and usb2 phy nodes for MT2701
Signed-off-by: Min Guo
---
changes in v4:
1. no changes
changes in v3:
1. no changes
changes in v2:
1. Remove phy-names
---
arch/arm/boot/dts/mt2701-evb.dts | 21 +
arch/arm/boot/dts/mt2701.dtsi| 33 ++
Hi
Felipe Balbi writes:
> Hi,
>
> Felipe Balbi writes:
>> Hi again,
>>
>> Felipe Balbi writes:
>>
>>
>>
>>> Try to dequeue a request that was already completed. Odd. Why are we
>>> missing a call to giveback??
>>
>> Got a little more information:
>>
>> file-storage-3982 [006] d... 131.
Add bindings for Marvell Armada 3700 USB2 UTMI+ PHY.
Signed-off-by: Miquel Raynal
---
.../bindings/phy/phy-mvebu-utmi.txt | 38 +++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
diff --git a/Documentation/
Marvell Armada 3700 SoC has two USB controllers, each of them being
wired to an internal UTMI PHY. Add a driver to control them.
Igal Liberman worked on supporting the PHY, I took the while 'register
configuration' from his work and rewrote almost entirely the
driver/bindings around it.
Co-develo
From: Ofer Heifetz
The mvebu xHCI host driver does not have suspend/resume support. Use of
the XHCI_RESET_ON_RESUME quirk is mandatory in order to avoid failures
after resume. This will work only if no USB device is plugged-in.
While at it, mention in the Kconfig file that this IP is also presen
Current implementation of the USB core does not take into account the
new PHY framework. Correct the situation by adding a call to
phy_set_mode() before phy_power_on().
Signed-off-by: Miquel Raynal
---
drivers/usb/core/hcd.c | 5 +
drivers/usb/core/phy.c | 28
d
Reference the PHY nodes from the USB controller nodes.
The USB3 host controller is wired to:
* the first PHY of the COMPHY IP
* the OTG-capable UTMI PHY
The USB2 host controller is wired to:
* the host-only UTMI PHY
Signed-off-by: Miquel Raynal
---
arch/arm64/boot/dts/marvell/armada-37xx
Hello,
As part of an effort to bring suspend to RAM support to Armada 3700
SoCs (main target: ESPRESSObin), this series handles the work around
the USB2 and USB32 IPs.
First, a change in the core adds support for the new PHY framework by
following the phy_set_mode()/phy_power_on() sequence (patch
The specification splits the USB2 memory region into three sections:
1/ 0xD005E000-0xD005EFFF: USB2 Host Controller Registers
2/ 0xD005F000-0xD005F7FF: USB2 UTMI PHY Registers
3/ 0xD005F800-0xD005: USB2 Host Miscellaneous Registers
Section 1/ belongs to the USB2 node but section 2/ belongs to
Update the Armada 3700 PHY drivers entry with the recently added UTMI
PHY driver.
Signed-off-by: Miquel Raynal
---
MAINTAINERS | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index abfd80f21b24..2a08a097e107 100644
--- a/MAINTAINERS
+++ b/MAINTAIN
On Marvell Armada 3700 SoCs there are two USB2 UTMI PHYs. They are
both very similar but only one has OTG/charging capabilities.
Because there are USB host registers and PHY registers mixed in a
single area, a system controller is also created and referenced from
both the USB host node and the PHY
Add suspend/resume callbacks to reset the host controller properly
during S2RAM operation.
Signed-off-by: Miquel Raynal
---
drivers/usb/host/ehci-orion.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/usb/host/ehci-orion.c b/drivers/usb/host/ehci-orion.c
i
No need to initialize the PHY from the driver's probe. It is done by
the core automatically and doing it twice would increment the
phy->powercount counter to 2 instead of 1. During later suspend
operation, the counter will be decremented to one, no phy->power_off()
will occur and worse than that, t
fixed the checkpatch.pl warning:
WARNING: Missing a blank line after declarations
Added space after declarations to conform to coding style.
Signed-off-by: Bharath Vedartham
---
drivers/usb/storage/karma.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/storage/karma.c b/driv
Hi Gregory,
Gregory CLEMENT wrote on Fri, 18 Jan 2019
17:04:01 +0100:
> Hi Miquel,
>
> On ven., janv. 11 2019, Miquel Raynal wrote:
>
> > From: Ofer Heifetz
> >
> > The mvebu xHCI host driver does not have suspend/resume support. Use of
> > the XHCI_RESET_ON_RESUME quirk is mandatory in or
Hi Kishon, Chunfeng,
Kishon Vijay Abraham I wrote on Wed, 16 Jan 2019
14:50:58 +0530:
> Hi,
>
> On 15/01/19 8:10 AM, Chunfeng Yun wrote:
> > Hi,
> > On Fri, 2019-01-11 at 14:31 +0100, Miquel Raynal wrote:
> >> Marvell Armada 3700 SoC has two USB controllers, each of them being
> >> wired to a
From: Yinbo Zhu
This patch is to add member has_fsl_erratum_a006918 in platform data
Signed-off-by: Yinbo Zhu
---
include/linux/fsl_devices.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/fsl_devices.h b/include/linux/fsl_devices.h
index 60cef82..7ea53c
From: Yinbo Zhu
This patch is to add member has_fsl_erratum_14 in platform data
Signed-off-by: Yinbo Zhu
---
include/linux/fsl_devices.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/fsl_devices.h b/include/linux/fsl_devices.h
index 7ea53c8..5c21a3a 100
Hi Gregory,
Gregory CLEMENT wrote on Fri, 18 Jan 2019
17:36:36 +0100:
> Hi Miquel,
>
> I have only a few smallish remarks:
>
> On ven., janv. 11 2019, Miquel Raynal wrote:
>
> > Marvell Armada 3700 SoC has two USB controllers, each of them being
> > wired to an internal UTMI PHY. Add a driv
From: Nikhil Badola
Remove USB errata checking code from driver. Applicability of erratum
is retrieved by reading corresponding property in device tree.
This property is written during device tree fixup.
Signed-off-by: Ramneek Mehresh
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
From: yinbo.zhu
USB erratum-A006918 workaround tries to start internal PHY inside
uboot (when PLL fails to lock). However, if the workaround also
fails, then USB initialization is also stopped inside Linux.
Erratum-A006918 workaround failure creates "fsl,erratum_a006918"
node in device-tree. Pres
From: Nikhil Badola
Set USB_EN bit to select ULPI phy for USB controller version 2.5
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
Change in v2:
replace Yinbo.Zhu with Yinbo Zhu
drivers/usb/host/ehci-fsl.c |6 ++
1 files changed, 6 insertions(+), 0 deleti
From: Suresh Gupta
PHY_CLK_VALID bit for UTMI PHY in USBDR does not set even
if PHY is providing valid clock. Workaround for this
involves resetting of PHY and check PHY_CLK_VALID bit
multiple times. If PHY_CLK_VALID bit is still not set even
after 5 retries, it would be safe to deaclare that PHY
-Original Message-
From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
Sent: 2019年1月21日 16:17
To: Yinbo Zhu ; Alan Stern
Cc: Xiaobo Xie ; Jerry Huang ; Ran
Wang ; Greg Kroah-Hartman ;
Ramneek Mehresh ; Nikhil Badola
; Suresh Gupta ;
linux-usb@vger.kernel.org; linux-ker
Hi Sergei,
Sergei Shtylyov wrote on Fri, 11
Jan 2019 21:03:01 +0300:
> Hello!
>
> On 01/11/2019 04:31 PM, Miquel Raynal wrote:
>
> > No need to initialize the PHY from the driver's probe. It is done by
> > the core automatically and doing it twice would increment the
> > phy->powercount counte
Hi Alexey,
On 2019-01-18 22:17, Alexey Khoroshilov wrote:
> If clk_prepare_enable() fails in dwc3_exynos_probe(),
> exynos->clks[0] is left undisabled because of usage
> preincrement in while condition.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Kh
Hi Gregory,
Gregory CLEMENT wrote on Fri, 18 Jan 2019
17:25:30 +0100:
> Hi Miquel,
>
> On ven., janv. 11 2019, Miquel Raynal wrote:
>
> > No need to initialize the PHY from the driver's probe. It is done by
> > the core automatically and doing it twice would increment the
>
> Do you know
For ISOC transfers, if there is no available data for a period, we need
to stop the transfer by issue a stop command, otherwise, all the
upcoming transfers will started by update transfer command, and will be
dropped with MISS ISOC errors.
Signed-off-by: Zeng Tao
---
drivers/usb/dwc3/gadget.c |
Hi balbi:
>-Original Message-
>From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
>Sent: Monday, January 14, 2019 4:13 PM
>To: Zengtao (B)
>Cc: Zengtao (B) ; Greg Kroah-Hartman
>; linux-usb@vger.kernel.org;
>linux-ker...@vger.kernel.org
>Subject: Re: [PATCH] usb: dwc3: gadget: don't
For OUT endpoints, zero-length transfers require MaxPacketSize buffer as
per the DWC_usb3 programming guide 3.30a section 4.2.3.3.
This patch fixes this by explicitly checking zero length
transfer to correctly pad up to MaxPacketSize.
Fixes: c6267a51639b (usb: dwc3: gadget: align transfers to
wMa
Hi,
Felipe Balbi writes:
> Hi again,
>
> Felipe Balbi writes:
>
>
>
>> Try to dequeue a request that was already completed. Odd. Why are we
>> missing a call to giveback??
>
> Got a little more information:
>
> file-storage-3982 [006] d... 131.010663: dwc3_ep_queue: ep1in: req
> 00
Hi again,
Felipe Balbi writes:
> Try to dequeue a request that was already completed. Odd. Why are we
> missing a call to giveback??
Got a little more information:
file-storage-3982 [006] d... 131.010663: dwc3_ep_queue: ep1in: req
eccaa10f length 0/16384 zsI ==> -115
fil
Hi,
"Zengtao (B)" writes:
>>-Original Message-
>>From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
>>Sent: Monday, January 14, 2019 4:13 PM
>>To: Zengtao (B)
>>Cc: Zengtao (B) ; Greg Kroah-Hartman
>>; linux-usb@vger.kernel.org;
>>linux-ker...@vger.kernel.org
>>Subject: Re: [PATCH
Hi,
"Zengtao (B)" writes:
>>-Original Message-
>>From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
>>Sent: Monday, January 21, 2019 4:17 PM
>>To: Zengtao (B)
>>Cc: Zengtao (B) ; Greg Kroah-Hartman
>>; linux-usb@vger.kernel.org;
>>linux-ker...@vger.kernel.org
>>Subject: Re: [PATCH
Hi balbi:
>-Original Message-
>From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
>Sent: Monday, January 21, 2019 4:17 PM
>To: Zengtao (B)
>Cc: Zengtao (B) ; Greg Kroah-Hartman
>; linux-usb@vger.kernel.org;
>linux-ker...@vger.kernel.org
>Subject: Re: [PATCH] usb: dwc3: gadget: issue
Hi,
Thinh Nguyen writes:
> On 1/17/2019 11:12 PM, Felipe Balbi wrote:
>> Hi,
>>
>> Thinh Nguyen writes:
>>> @@ -1409,15 +1407,11 @@ static int dwc3_gadget_ep_dequeue(struct usb_ep *ep,
>>> if (r == req) {
>>> /* wait until it is processed */
>>>
Hi Heikki,
On 2018/12/3 20:25, Heikki Krogerus wrote:
> Hi,
>
> On Mon, Dec 03, 2018 at 10:17:20AM +0200, Andy Shevchenko wrote:
>> On Mon, Dec 3, 2018 at 5:45 AM Yu Chen wrote:
>>>
>>> This patch adds code for supporting find usb role switch by matching against
>>> the device node described usi
Hi,
Zeng Tao writes:
> For ISOC transfers, if there is no available data for a period, we need
> to stop the transfer by issue a stop command, otherwise, all the
> upcoming transfers will started by update transfer command, and will be
> dropped with MISS ISOC errors.
We, actually, have code to
Hello!
On 21.01.2019 6:13, Yinbo Zhu wrote:
From: yinbo.zhu
USB erratum-A006918 workaround tries to start internal PHY inside
uboot (when PLL fails to lock). However, if the workaround also
fails, then USB initialization is also stopped inside Linux.
Erratum-A006918 workaround failure creates
From: Christophe Leroy
Since only the virtual address of allocated blocks is used,
lets use functions returning directly virtual address.
Those functions have the advantage of also zeroing the block.
[ MR:
- updated error message in alloc_stack() to be more verbose
- convereted several additi
Hi,
Current memblock API is quite extensive and, which is more annoying,
duplicated. Except the low-level functions that allow searching for a free
memory region and marking it as reserved, memblock provides three (well,
two and a half) sets of functions to allocate memory. There are several
overl
Rename memblock_alloc_range() to memblock_phys_alloc_range() to emphasize
that it returns a physical address.
While on it, remove the 'enum memblock_flags' parameter from this function
as its only user anyway sets it to MEMBLOCK_NONE, which is the default for
the most of memblock allocations.
Sign
Make the memblock_phys_alloc() function an inline wrapper for
memblock_phys_alloc_range() and update the memblock_phys_alloc() callers to
check the returned value and panic in case of error.
Signed-off-by: Mike Rapoport
---
arch/arm/mm/init.c | 4
arch/arm64/mm/mmu.c
The memblock_alloc_base_nid() is a oneliner wrapper for
memblock_alloc_range_nid() without any side effect.
Replace it's usage by the direct calls to memblock_alloc_range_nid().
Signed-off-by: Mike Rapoport
---
include/linux/memblock.h | 3 ---
mm/memblock.c| 15 ---
2 f
The __memblock_alloc_base() function tries to allocate a memory up to the
limit specified by its max_addr parameter. Depending on the value of this
parameter, the __memblock_alloc_base() can is replaced with the appropriate
memblock_phys_alloc*() variant.
Signed-off-by: Mike Rapoport
Acked-by: Ro
These functions are not used outside memblock. Make them static.
Signed-off-by: Mike Rapoport
---
include/linux/memblock.h | 4
mm/memblock.c| 4 ++--
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index cf4cd9c
The last parameter of memblock_alloc_from() is the lower limit for the
memory allocation. When it is 0, the call is equivalent to
memblock_alloc().
Signed-off-by: Mike Rapoport
Acked-by: Paul Burton # MIPS part
---
arch/alpha/kernel/core_cia.c | 2 +-
arch/alpha/kernel/pci_iommu.c | 4 ++--
memblock_alloc() already clears the allocated memory, no point in doing it
twice.
Signed-off-by: Mike Rapoport
Acked-by: Geert Uytterhoeven # m68k
---
arch/c6x/mm/init.c | 1 -
arch/h8300/mm/init.c| 1 -
arch/ia64/kernel/mca.c | 2 --
arch/m68k/mm/mcfmmu.c | 1 -
arc
From: Suresh Gupta
PHY_CLK_VALID bit for UTMI PHY in USBDR does not set even
if PHY is providing valid clock. Workaround for this
involves resetting of PHY and check PHY_CLK_VALID bit
multiple times. If PHY_CLK_VALID bit is still not set even
after 5 retries, it would be safe to deaclare that PHY
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
mm/percpu.c | 73 ++
This patch is to add member has_fsl_erratum_14 in platform data
Signed-off-by: Yinbo Zhu
---
include/linux/fsl_devices.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/fsl_devices.h b/include/linux/fsl_devices.h
index 7ea53c8..5c21a3a 100644
--- a/include/
Add panic() calls if memblock_alloc*() returns NULL.
Most of the changes are simply addition of
if(!ptr)
panic();
statements after the calls to memblock_alloc*() variants.
Exceptions are pcpu_populate_pte() and kernel_map_range() that were
slightly refactored to accommod
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
kernel/dma/swiotlb.
Currently, memblock has several internal functions with overlapping
functionality. They all call memblock_find_in_range_node() to find free
memory and then reserve the allocated range and mark it with kmemleak.
However, there is difference in the allocation constraints and in fallback
strategies.
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
init/main.c | 26 ++
As all the memblock allocation functions return NULL in case of error
rather than panic(), the duplicates with _nopanic suffix can be removed.
Signed-off-by: Mike Rapoport
Acked-by: Greg Kroah-Hartman
---
arch/arc/kernel/unwind.c | 3 +--
arch/sh/mm/init.c | 2 +-
arch/x86/
The memblock_phys_alloc_try_nid() function tries to allocate memory from
the requested node and then falls back to allocation from any node in the
system. The memblock_alloc_base() fallback used by this function panics if
the allocation fails.
Replace the memblock_alloc_base() fallback with the di
1 - 100 of 110 matches
Mail list logo
