On Thu, Aug 1, 2019 at 12:53 AM Russell King - ARM Linux admin
wrote:
>
> On Wed, Jul 31, 2019 at 09:56:42PM +0200, Arnd Bergmann wrote:
> > For dove, the patches are basically what I had proposed back in
> > 2015 when all other ARMv6/ARMv7 machines became part of a single
> > kernel build. I don'
There is no need to use GFP_ATOMIC when calling 'usb_alloc_coherent()'
here. These calls are done from probe functions and using GFP_KERNEL should
be safe.
The memory itself is used within some interrupts, but it is not a
problem, once it has been allocated.
Signed-off-by: Christophe JAILLET
---
Fix smatch error:
drivers/usb/typec/ucsi/ucsi_ccg.c:975 ccg_fw_update() error: uninitialized
symbol 'err'.
Fixes: 5c9ae5a87573 ("usb: typec: ucsi: ccg: add firmware flashing support")
Cc: sta...@vger.kernel.org
Reported-by: kbuild test robot
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec
Hi everyone,
I am trying to get Renesas uPD720202 USB3.0 hub working which is
connected PCIe switch (PEX8605); PEX8605 is connected to i.MX6Q
through its x1 PCIe Gen2 interface. Running Linux-4.19.25 vanilla
kernel with patches from Phytec.de for their Phycore-iMX6Q SOM.
We have 2x PEX8605 ports
For consistency with the naming of (most) other documentation files for DT
bindings for Renesas IP blocks rename the Renesas USB3.0 peripheral
documentation file from renesas,gen3.txt to renesas,usb3-peri.txt
This refines a recent rename from renesas,gen3.txt to renesas-gen3.txt.
The motivation is
On Mon, Jul 29, 2019 at 08:25:24AM +, Yoshihiro Shimoda wrote:
> Hi Simon-san,
>
> > From: Simon Horman, Sent: Monday, July 29, 2019 5:15 PM
>
> > > > > > Unfortunately the previous version has already made it into usb-next
> > > > > > 23c46801d14cb647 dt-bindings: usb: renesas_gen3: Rename b
On Thu, Aug 1, 2019 at 11:13 AM Simon Horman wrote:
> For consistency with the naming of (most) other documentation files for DT
> bindings for Renesas IP blocks rename the Renesas USB3.0 peripheral
> documentation file from renesas,gen3.txt to renesas,usb3-peri.txt
from renesas,usb3.txt
> This
On Thu, Aug 01, 2019 at 11:18:36AM +0200, Geert Uytterhoeven wrote:
> On Thu, Aug 1, 2019 at 11:13 AM Simon Horman
> wrote:
> > For consistency with the naming of (most) other documentation files for DT
> > bindings for Renesas IP blocks rename the Renesas USB3.0 peripheral
> > documentation file
Am 01.08.2019 09:47, schrieb Christophe JAILLET:
> There is no need to use GFP_ATOMIC when calling 'usb_alloc_coherent()'
> here. These calls are done from probe functions and using GFP_KERNEL should
> be safe.
> The memory itself is used within some interrupts, but it is not a
> problem, once i
Hello,
syzbot found the following crash on:
HEAD commit:7f7867ff 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=13efa03060
kernel config: https://syzkaller.appspot.com/x/.
Hi
On 01/08/2019 11:38, syzbot wrote:
Hello,
syzbot found the following crash on:
HEAD commit:7f7867ff 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=13efa03060
kernel co
On 2019-07-31 6:47 p.m., Douglas Gilbert wrote:
On 2019-07-24 4:38 p.m., Guenter Roeck wrote:
When instantiating tcpm on an NXP OM 13588 board with NXP PTN5110,
the following crash is seen when writing into the 'preferred_role'
sysfs attribute.
Unable to handle kernel NULL pointer dereference a
On Thu, Aug 01, 2019 at 12:06:03PM +0200, walter harms wrote:
>
>
> Am 01.08.2019 09:47, schrieb Christophe JAILLET:
> > There is no need to use GFP_ATOMIC when calling 'usb_alloc_coherent()'
> > here. These calls are done from probe functions and using GFP_KERNEL should
> > be safe.
> > The memo
On 8/1/19 12:38 AM, Suwan Kim wrote:
On Mon, Jul 29, 2019 at 10:32:31AM -0600, shuah wrote:
On 7/29/19 8:52 AM, Suwan Kim wrote:
Hi Shuah,
On Tue, Jul 23, 2019 at 06:21:53PM -0600, shuah wrote:
Hi Suwan,
On 7/5/19 10:43 AM, Suwan Kim wrote:
There are bugs on vhci with usb 3.0 storage device
Hi Matthew,
On Thu, Aug 01, 2019 at 01:16:34PM +0100, Matthew Nicholson wrote:
> [Resending as plain text email with attachments.]
>
> Hi,
> The kernel version testing I'm testing on is: v5.2.4-arch1
> I have disabled gmd, which seems to struggle with not being able to
> configure displays and b
Hi All,
I am seeing a peculiar behaviour which I think *might* be
caused by usb_new_device(). Since usb_new_device() is one of the core
APIs, I cannot explain how PM works for USB device at later point in
time.
In a particular use-case, our composite USB device
exposes HID interface with vendor
Hello,
syzbot found the following crash on:
HEAD commit:e96407b4 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=147ac20c60
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:7f7867ff 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=17ab6aec60
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:7f7867ff 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=136b6aec60
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:41550654 [UPSTREAM] KVM: x86: degrade WARN to pr_warn_rate..
git tree: kmsan
console output: https://syzkaller.appspot.com/x/log.txt?x=13a0b07da0
kernel config: https://syzkaller.appspot.com/x/.config?x=40511ad0c5945201
dashb
Hello,
syzbot found the following crash on:
HEAD commit:7829a896 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=1211944060
kernel config: https://syzkaller.appspot.com/x/.
On Tue, Jul 23, 2019 at 4:28 PM syzbot
wrote:
>
> 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=13f6
On Wed, Jul 31, 2019 at 12:55:55PM +0300, Heikki Krogerus wrote:
> On Tue, Jul 30, 2019 at 06:28:52AM -0700, Guenter Roeck wrote:
> > On 7/30/19 5:07 AM, Heikki Krogerus wrote:
> > > On Mon, Jul 29, 2019 at 10:31:04AM -0700, Guenter Roeck wrote:
> > > > On Mon, Jul 29, 2019 at 05:04:57PM +0300, Hei
[+cc i.MX6 folks]
On Thu, Aug 01, 2019 at 10:18:22AM +0200, Fawad Lateef wrote:
> Hi everyone,
>
> I am trying to get Renesas uPD720202 USB3.0 hub working which is
> connected PCIe switch (PEX8605); PEX8605 is connected to i.MX6Q
> through its x1 PCIe Gen2 interface. Running Linux-4.19.25 vanilla
On Thu, 1 Aug 2019, Mayuresh Kulkarni wrote:
> Hi All,
>
> I am seeing a peculiar behaviour which I think *might* be
> caused by usb_new_device(). Since usb_new_device() is one of the core
> APIs, I cannot explain how PM works for USB device at later point in
> time.
>
> In a particular use-cas
On Thu, 1 Aug 2019, Andrey Konovalov wrote:
> On Tue, Jul 23, 2019 at 4:28 PM syzbot
> wrote:
> >
> > 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
>
From: Gavin Li
On architectures that are not (or are optionally) DMA coherent,
dma_alloc_coherent() returns an address into the vmalloc space,
and calling virt_to_phys() on this address returns an unusable
physical address.
This patch replaces the raw remap_pfn_range() call with a call to
dmap_m
From: Gavin Li
On architectures that are not (or are optionally) DMA coherent,
dma_alloc_coherent() returns an address into the vmalloc space,
and calling virt_to_phys() on this address returns an unusable
physical address.
This patch replaces the raw remap_pfn_range() call with a call to
dmap_m
28 matches
Mail list logo
