This patch simply adds a new PCI Device ID
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/dwc3-pci.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c
index 8cced3609e24..f9b550081550 100644
--- a/drivers/usb/dwc3/dwc3-pci.c
+++ b
From: "Lee, Chiasheng"
With Link Power Management (LPM) enabled USB3 links transition to low
power U1/U2 link states from U0 state automatically.
Current hub code detects USB3 remote wakeups by checking if the software
state still shows suspended, but the link has transitioned from suspended
U3
From: Kiruthika Varadarajan
During gadget connection/disconnect several times panic observed.
[ 64.723260] BUG: unable to handle kernel NULL pointer dereference at
00f0
[ 64.732040] IP: [] rx_fill+0x1ed/0x3b0
[ 64.737984] PGD 6bece067 PUD 0
[ 64.741503] Oops: [#1] PREEMPT SMP
Hi Greg,
Just one pending fix this time.
Let me know if you need anything to be changed
cheers
The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/li
On Thu, Jun 20, 2019 at 12:13:01PM +0300, Felipe Balbi wrote:
>
> Hi Greg,
>
> Just one pending fix this time.
>
> Let me know if you need anything to be changed
>
> cheers
>
>
> The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec:
>
> Linux 5.2-rc5 (2019-06-16 08:4
On Mon, Jun 10, 2019 at 02:32:16PM +1200, Jonathan Olds wrote:
> Hi Johan,
>
> Thanks for the info. I followed
> https://nickdesaulniers.github.io/blog/2017/05/16/submitting-your-first-patc
> h-to-the-linux-kernel-and-responding-to-feedback/ and made a proposal patch
> ("[PATCH] USB: serial: ch341
On Sat, Jun 08, 2019 at 05:13:09PM +1200, jontio wrote:
> For some wanted baud rates ch341_set_baudrate_lcr() calculates the "a"
> value such that it produces a significantly different baud rate than the
> desired one. This means some hardware can't communicate with the CH34x
> chip. Particularly o
On Wed, 2019-06-19 at 11:19 +0200, Oliver Neukum wrote:
> Am Dienstag, den 18.06.2019, 11:50 -0400 schrieb Alan Stern:
> >
> > On Tue, 18 Jun 2019, Mayuresh Kulkarni wrote:
> >
> > >
> > > >
> > > > You're right that the program needs to know when the device is
> > > > about
> > > > to
> > > >
On Thu, 20 Jun 2019, Mayuresh Kulkarni wrote:
> > It would be easiest to export the usb_autopm_* API to user space.
>
> AFAIU, usb_autopm_* API operate on interface rather than on device.
> Due to this, they are *indirectly* exposed by appropriate class drivers
> to the user-space class drivers c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
head: f1ac9f310d6d883b3551f4cb948eb441c780b59d
commit: f1ac9f310d6d883b3551f4cb948eb441c780b59d [46/46] usb: clean up some of
the computations in adu_read
config: sh-allmodconfig (attached as .config)
compiler: s
kbuild test robot writes:
[...]
>
> All warnings (new ones prefixed by >>):
>
>In file included from include/linux/printk.h:332:0,
> from include/linux/kernel.h:15,
> from drivers/usb//misc/adutux.c:19:
>drivers/usb//misc/adutux.c: In function 'ad
On Wed, 2019-06-19 at 10:40 -0400, Alan Stern wrote:
> On Wed, 19 Jun 2019, Oliver Neukum wrote:
>
> >
> > Am Dienstag, den 18.06.2019, 11:50 -0400 schrieb Alan Stern:
> > >
> > > On Tue, 18 Jun 2019, Mayuresh Kulkarni wrote:
> > >
> > > >
> > > > >
> > > > > You're right that the program nee
On Thu, Jun 20, 2019 at 08:01:30AM -0700, dmg wrote:
>
> kbuild test robot writes:
>
> [...]
> >
> > All warnings (new ones prefixed by >>):
> >
> >In file included from include/linux/printk.h:332:0,
> > from include/linux/kernel.h:15,
> > from drivers
On Thu, 20 Jun 2019, dmg wrote:
>
> kbuild test robot writes:
>
> [...]
> >
> > All warnings (new ones prefixed by >>):
> >
> >In file included from include/linux/printk.h:332:0,
> > from include/linux/kernel.h:15,
> > from drivers/usb//misc/adutux.c:
On Thu, 20 Jun 2019, Mayuresh Kulkarni wrote:
> On Wed, 2019-06-19 at 10:40 -0400, Alan Stern wrote:
> > The only solution I can think of is for the userspace program to first
> > set the device's autosuspend delay to 0. Then whenever the
> > WAIT_FOR_RESUME ioctl returns -- even if it returns i
Hi,
Thinh Nguyen wrote:
> Felipe Balbi wrote:
>> Hi,
>>
>> Thinh Nguyen writes:
>>> Would there be any obvious draw-back to going down this route? The thing
>>> is that, as it is, it seems like we will *always* have some corner case
>>> where we can't guarantee that we can even start
On Mon, Jun 3, 2019 at 12:46 PM Oliver Neukum wrote:
>
> Am Samstag, den 01.06.2019, 09:52 +0200 schrieb Marco Zatta:
> > This patch fixes the chipmunk-like voice that manifets randomly when
> > using the integrated mic of the Logitech Webcam HD C270.
> >
> > The issue was solved initially for thi
On Thu, Jun 20, 2019 at 08:01:30AM -0700, dmg wrote:
>
> kbuild test robot writes:
>
> [...]
> >
> > All warnings (new ones prefixed by >>):
> >
> >In file included from include/linux/printk.h:332:0,
> > from include/linux/kernel.h:15,
> > from drivers
From: Daniel M German
Replace ?: with min to calculate the number of bytes in the secondary buffer,
including changing the data type of data_in_secondary to size_t to be
type-consistent. data_in_secondary can never be negative.
Remove some spurious calculations (copy_to_user returns zero on succ
19 matches
Mail list logo
