Good Morning,
HAPPY NEW YEAR.
I am Edwin Clark, I am contacting regarding your late relative who
bears the same last name with you , I have been searching for you for
a longtime without any luck.
I await your response for more details.
Edwin Clark.
+228-96558071.
USB Bluetooth controller QCA ROME (0cf3:e007) sometimes stops working
after S3:
[ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
[ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
After some experiments, I found that disabling LPM can workaround the
issue
Use new helpers to make LPM enabling/disabling more clear.
This is a preparation to subsequent patch.
Signed-off-by: Kai-Heng Feng
---
v5:
- Split to two patches. The first one uses the new LPM helpers, the
second one consolidates the LPM checks to solve the issue.
v4:
- Use usb_enable_usb2
On 1/11/2019 12:45 PM, Rob Herring wrote:
On Fri, Jan 04, 2019 at 09:50:47AM -0700, Jeffrey Hugo wrote:
MSM8998 contains a single QMP v3 USB3 phy similar to the existing sdm845
support, however MSM8998 does not have display port (DP) support.
Signed-off-by: Jeffrey Hugo
---
.../devicetree/bi
On Fri, Jan 04, 2019 at 09:50:47AM -0700, Jeffrey Hugo wrote:
> MSM8998 contains a single QMP v3 USB3 phy similar to the existing sdm845
> support, however MSM8998 does not have display port (DP) support.
>
> Signed-off-by: Jeffrey Hugo
> ---
> .../devicetree/bindings/phy/qcom-qmp-phy.txt
Am 11.01.19 um 19:20 schrieb Oliver Neukum:
> On Fr, 2019-01-11 at 15:39 +0100, Jan-Marek Glogowski wrote:
>> I've got new hardware (Acer s4640g), which has some USB 3.1 gen 2 usb-c
>> ports.
>>
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
>> |__ Port 3: Dev 2, If
On Fri, 11 Jan 2019, Paul Elder wrote:
> On Thu, Jan 10, 2019 at 03:39:25PM -0500, Alan Stern wrote:
> > On Wed, 9 Jan 2019, Paul Elder wrote:
> >
> > > This patch series adds a mechanism to allow asynchronously validating
> > > the data stage of a control OUT request, and for stalling or suceedi
On Fr, 2019-01-11 at 15:39 +0100, Jan-Marek Glogowski wrote:
> I've got new hardware (Acer s4640g), which has some USB 3.1 gen 2 usb-c ports.
>
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
> |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
Acco
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 counter to 2 instead of 1. During later suspend
> operation, the counter will be decremented
The patch "usb: simplify usbport trigger" together with
"leds: triggers: add device attribute support" caused an
regression for the usbport trigger. it will no longer
enumerate any active usb hub ports under the "ports"
directory in the sysfs class directory, if the usb host
drivers are fully initi
On Fri, 11 Jan 2019, Paul Elder wrote:
> On Wed, Jan 09, 2019 at 02:06:31PM -0500, Alan Stern wrote:
> > On Wed, 9 Jan 2019, Paul Elder wrote:
> >
> > > A usb gadget function driver may or may not want to delay the status
> > > stage of a control OUT request. An instance where it might want to is
Hi,
I've got new hardware (Acer s4640g), which has some USB 3.1 gen 2 usb-c ports.
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
|__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
I have installed our current Ubuntu 18.04 based release with the incl
Hi,
david preetham writes:
> Dear Balbi,
>
> In DWC3 USB device controller, on which basis event->status &
> DEPEVT_STATUS_SHORT is set
when we have a short packet
> who will set? I understand if we receive less bytes we are going to
HW will set it
> set short packet.
>
> Suppose gadget driv
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
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
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 worst than that, t
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
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
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
Add bindings for Marvell Armada 3700 USB2 UTMI+ PHY.
Signed-off-by: Miquel Raynal
---
.../bindings/phy/phy-mvebu-utmi.txt | 37 +++
1 file changed, 37 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
diff --git a/Documentation/
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 Fr, 2019-01-11 at 10:10 +0100, Greg KH wrote:
> On Thu, Jan 10, 2019 at 01:10:25PM +0530, Sabyasachi Gupta wrote:
> > Remove unusual_sddr55.h which is included more than once
> >
> > Signed-off-by: Sabyasachi Gupta
> > ---
> > drivers/usb/storage/sddr55.c | 1 -
> > 1 file changed, 1 deletion
Ok, sorry it was my bad, I had the usb_autopm_get_interface in the wrong place:
there was an even earlier call to
usb_control_msg, which is why things didn't work.
As the next step I'm going to prepare a patch to fix this buggy interaction
with PM. Assuming GPIO pin state is not lost in suspend
Hi,
Manu Gautam writes:
>> Manu Gautam writes:
>>> If a function driver tries to re-submit an already queued request,
>>> it can results in corruption of pending/started request lists.
>>> Catch such conditions and fail the request submission to DCD.
>>>
>>> Signed-off-by: Manu Gautam
>>> ---
On Tue, Jan 08, 2019 at 12:34:17PM -0500, Alan Stern wrote:
> On Wed, 9 Jan 2019, Kai Heng Feng wrote:
>
> > > On Jan 8, 2019, at 11:41 PM, Greg KH wrote:
> > >
> > > On Mon, Dec 03, 2018 at 06:26:43PM +0800, Kai-Heng Feng wrote:
> > >> USB Bluetooth controller QCA ROME (0cf3:e007) sometimes sto
On Thu, Jan 10, 2019 at 12:19:36PM +0530, Sabyasachi Gupta wrote:
> Remove unusual_cypress.h which is included more than once.
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/cypress_atacb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/usb/storage/cypress_atac
Hi Alan,
On Thursday, January 10, 2019, Alan wrote:
>
> On Thu, 10 Jan 2019, Ran Wang wrote:
>
> > Hi Alan,
> >
> > > -Original Message-
> > > From: Alan Stern
> > > Sent: Wednesday, January 09, 2019 23:14
> > > To: Ran Wang
> > > Cc: Greg Kroah-Hartman ; linux-
> > > u...@vger.kernel.
On Thu, Jan 10, 2019 at 12:40:07PM +0530, Sabyasachi Gupta wrote:
> Remove duplicate headers which are included more than once.
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/datafab.c| 1 -
> drivers/usb/storage/ene_ub6250.c | 1 -
> 2 files changed, 2 deletions(-)
>
> dif
On Thu, Jan 10, 2019 at 01:10:25PM +0530, Sabyasachi Gupta wrote:
> Remove unusual_sddr55.h which is included more than once
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/sddr55.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/usb/storage/sddr55.c b/drivers/us
On Thu, Jan 10, 2019 at 10:49:09AM -0500, Kyle Williams wrote:
> On Wed, Dec 12, 2018 at 12:37:09PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 07, 2018 at 08:47:21PM -0500, Kyle Williams wrote:
> > > From: Kyle Williams
> > >
> > > Description: enable the ability to disable LPM for all devi
On Thu, Jan 10, 2019 at 03:39:25PM -0500, Alan Stern wrote:
> On Wed, 9 Jan 2019, Paul Elder wrote:
>
> > This patch series adds a mechanism to allow asynchronously validating
> > the data stage of a control OUT request, and for stalling or suceeding
> > the request accordingly.
>
> One thing we
Hi,
On 1/11/2019 1:13 PM, Felipe Balbi wrote:
> Hi,
>
> Manu Gautam writes:
>> If a function driver tries to re-submit an already queued request,
>> it can results in corruption of pending/started request lists.
>> Catch such conditions and fail the request submission to DCD.
>>
>> Signed-off-by:
On Wed, Jan 09, 2019 at 02:06:31PM -0500, Alan Stern wrote:
> On Wed, 9 Jan 2019, Paul Elder wrote:
>
> > A usb gadget function driver may or may not want to delay the status
> > stage of a control OUT request. An instance where it might want to is to
> > asynchronously validate the data of a clas
On Thu, Jan 10, 2019 at 11:21:03PM +, Karoly Pados wrote:
> Hello,
>
> It was observed that the GPIOs of the ftdi_sio driver cannot be used
> when the device was put into autosuspend earlier (usb_control_msg returns
> -EHOSTUNREACH). Quick workaround for users is to disable autosuspend only
>
37 matches
Mail list logo
