Dear All,
Commit 69bec7259853 ("USB: core: let USB device know device node") added
support for attaching devicetree node for USB devices. Those nodes are
children of their USB host controller. However Exynos EHCI and OHCI
driver bindings already define child-nodes for each physical root hub
port a
Move USB PHYs to a standard arrays for Exynos EHCI/OHCI devices. This
resolves the conflict between Exynos EHCI/OHCI sub-nodes and generic USB
device bindings. Once the Exynos EHCI/OHCI sub-nodes are removed, the
boards can finally provide sub-nodes for the USB devices using generic USB
device bind
Commit 69bec7259853 ("USB: core: let USB device know device node") added
support for attaching devicetree node for USB devices. Those nodes are
children of their USB host controller. However Exynos EHCI and OHCI
driver bindings already define child-nodes for each physical root hub
port and assigns
Add the code for getting generic PHYs from standard device tree array
from the main controller device node. This is a first step in resolving
the conflict between Exynos EHCI/OHCI sub-nodes and generic USB device
bindings. Later the sub-nodes currently used for assigning PHYs to root
ports of the c
On 24.7.2019 22.09, Daniele Palmas wrote:
Hello all,
I've a system with kernel 4.14.127 that is showing unexpected xhci-hcd
(ASM1042A) errors with a Qualcomm based modem, when running the
following test:
- signal strength qmi requests looping every few seconds on
/dev/cdc-wdm (driver qmi_wwan)
On Fri, 26 Jul 2019 at 10:15, Marek Szyprowski wrote:
>
> Commit 69bec7259853 ("USB: core: let USB device know device node") added
> support for attaching devicetree node for USB devices. Those nodes are
> children of their USB host controller. However Exynos EHCI and OHCI
> driver bindings alread
On Fri, 26 Jul 2019 at 10:15, Marek Szyprowski wrote:
>
> Add the code for getting generic PHYs from standard device tree array
> from the main controller device node. This is a first step in resolving
> the conflict between Exynos EHCI/OHCI sub-nodes and generic USB device
> bindings. Later the s
On Fri, 26 Jul 2019 at 10:15, Marek Szyprowski wrote:
>
> Move USB PHYs to a standard arrays for Exynos EHCI/OHCI devices. This
> resolves the conflict between Exynos EHCI/OHCI sub-nodes and generic USB
> device bindings. Once the Exynos EHCI/OHCI sub-nodes are removed, the
> boards can finally pr
Hello,
syzbot found the following crash on:
HEAD commit:6a3599ce usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=164ab1f060
kernel config: https://syzkaller.appspot.com/x/.
On Fri, 26 Jul 2019, Marek Szyprowski wrote:
> Add the code for getting generic PHYs from standard device tree array
> from the main controller device node. This is a first step in resolving
> the conflict between Exynos EHCI/OHCI sub-nodes and generic USB device
> bindings. Later the sub-nodes cu
Hi Mathias,
Il giorno ven 26 lug 2019 alle ore 10:50 Mathias Nyman
ha scritto:
>
> On 24.7.2019 22.09, Daniele Palmas wrote:
> > Hello all,
> >
> > I've a system with kernel 4.14.127 that is showing unexpected xhci-hcd
> > (ASM1042A) errors with a Qualcomm based modem, when running the
> > follow
On 2019-07-25 12:30 a.m., Guenter Roeck wrote:
TCPM may receive PD messages associated with unknown or unsupported
alternate modes. If that happens, calls to typec_match_altmode()
will return NULL. The tcpm code does not currently take this into
account. This results in crashes.
Unable to handle
Attn Dear Atm Card beneficiary.
GOOD NEWS,
This is to inform you that i have paid the delivery fees for your ATM
Master Card
I paid it because our bank director stated that before, they
So contact Dr. William Roberts, Director DHL Courier
Company Benin to receive your delivery ATM Visa Card amount
From: "Angus Ainslie (Purism)"
Date: Wed, 24 Jul 2019 07:52:27 -0700
> From: Bob Ham
>
> The BroadMobi BM818 M.2 card uses the QMI protocol
>
> Signed-off-by: Bob Ham
> Signed-off-by: Angus Ainslie (Purism)
Applied, thanks.
Hello,
I have seen kernel oopses on waking from suspend to memory. I got this
twice, one dmesg with backtrace attached. The other one had the failure
in the same place in the code.
This is kernel 5.3.0-rc1, patched for another problem in ethernet PHY
driver. Have not had the problem with earlie
15 matches
Mail list logo