Hi,
On Tue, Nov 15, 2016 at 01:37:49PM -0800, Tony Lindgren wrote:
> Hi all,
>
> Here's v3 of musb fixes for issues that I've been able to track down.
> The PM changes merged for v4.9 popped up various issues reported by
> people that I had not seen earlier with my tests.
>
> As many people
Add check for NULL before calling kthread_stop().
There were cases in which gserial_console_exit() was called, but the
console thread was not started. This resulted in an invalid
kthread_stop(NULL) call.
Signed-off-by: Felix Hädicke
---
There can be cases when members of the gscons_info struct are used
uninitialized, e. g. in, gserial_console_exit(), if gs_console_setup()
was not called before.
Signed-off-by: Felix Hädicke
---
drivers/usb/gadget/function/u_serial.c | 2 +-
1 file changed, 1 insertion(+),
> > This will make option grab all the ports, as shown by your dmesg
> > output. But USB interfaces 0 and 1 are actually cdc-ether and should
> > *not* be grabbed by option.
I also have another curiosity:
Why the driver architecture doesn't recognize autonomously the cdc-ether
Interface and only
From: Tony Lindgren
We can't use static variable first for checking when musb is
initialized when we have multiple musb instances like on am335x.
Tested-by: Ladislav Michl
Reviewed-by: Johan Hovold
Tested-by: Laurent Pinchart
From: Tony Lindgren
Commit 65b3f50ed6fa ("usb: musb: Add PM runtime support for MUSB DSPS
glue layer") wrongly added a call for pm_runtime_get_sync to otg_timer
that runs in softirq context. That causes a "BUG: sleeping function called
from invalid context" every time when
Hi Greg,
Hope this is not too late for -rc6. This set fixes a long standing musb
regression introduced in v4.8. Please let me know if any change is needed.
Thanks,
-Bin.
---
Tony Lindgren (6):
usb: musb: Fix broken use of static variable for multiple instances
usb: musb: Fix sleeping
From: Tony Lindgren
We are missing pm_runtime_disable() in 2430 glue layer. Further,
we only need to enable PM runtime and disable it on exit. With
musb_core.c doing PM, the glue layer as a parent will always be
active when musb_core.c is active.
This fixes host enumeration
From: Tony Lindgren
Now with musb driver implementing generic session bit based
PM, we need to have the USB PHYs behaving in a sane way for
platforms implementing PM.
Currently twl4030-usb enables PM in twl4030_phy_power_on()
and then disables it in twl4030_phy_power_off().
From: Tony Lindgren
With a USB hub disconnected, devctl can be 0x19 for about a second
on am335x and will stay forever on at least omap3. And we get no
further interrupts when devctl session bit clears. This keeps
PM runtime active.
Let's fix the issue by polling devctl until
From: Tony Lindgren
This already gets done automatically by PM runtime and we have
a separate autosuspend timeout in musb_core.c.
Reviewed-by: Johan Hovold
Tested-by: Laurent Pinchart
Signed-off-by: Tony Lindgren
On 11/16/2016 1:25 AM, Stefan Wahren wrote:
> Hi John,
>
>> John Youn hat am 16. November 2016 um 01:36
>> geschrieben:
>>
>>
>> The ahbcfg param for bcm2835 is specifying a HBSTLEN of 0x8 (0x10 >> 1)
>> which is not a valid value for that field. Remove the param and
Hi,
For me, it is always reproducible when CONFIG_U_SERIAL_CONSOLE is enabled.
But I think that GDB is misleading, it has probably nothing to do with
gs_buf_free(). For me, it looks like the real problem is that in
gserial_console_exit(), kthread_stop() is called on the (in my case)
Hello.
On 11/16/2016 11:46 PM, Felix Hädicke wrote:
There can be cases when members of the gscons_info struct are used
uninitialized, e. g. in, gserial_console_exit(), if gs_console_setup()
was not called before.
Signed-off-by: Felix Hädicke
---
Dear All,
thanks for the very interesting discussion.
> > This will make option grab all the ports, as shown by your dmesg
> > output. But USB interfaces 0 and 1 are actually cdc-ether and should
> > *not* be grabbed by option.
> >
> > You want to limit option to grabbing bInterfaceClass=255 to
On Wed, 2016-11-16 at 11:49 -0600, Dan Williams wrote:
> This will make option grab all the ports, as shown by your dmesg
> output. But USB interfaces 0 and 1 are actually cdc-ether and should
> *not* be grabbed by option.
>
> You want to limit option to grabbing bInterfaceClass=255 to make sure
ok, thanks for the hint. I dind't know this.
Just ignore this patch.
Am 16.11.2016 um 22:42 schrieb Sergei Shtylyov:
> Hello.
>
> On 11/16/2016 11:46 PM, Felix Hädicke wrote:
>
>> There can be cases when members of the gscons_info struct are used
>> uninitialized, e. g. in,
From: Razmik Karapetyan
Removed extern specifier from dwc2_host_start(), dwc2_host_disconnect()
and dwc2_host_hub_info() functions. Moved those functions from header
to source. Then make them static.
Signed-off-by: Razmik Karapetyan
Signed-off-by: John
From: Razmik Karapetyan
Remove request length checking from dwc2_hsotg_unmap_dma() and
dwc2_hsotg_map_dma(). That checking is done in functions called from
those functions, usb_gadget_unmap_request_by_dev() and
usb_gadget_map_request_by_dev() respectively, so it's
From: Razmik Karapetyan
NPTXFIFO's start address is showing 0x0300 instead of 0x0800.
Replaced val & FIFOSIZE_DEPTH_MASK by val & FIFOSIZE_STARTADDR_MASK in
fifo_show() function.
Signed-off-by: Razmik Karapetyan
Signed-off-by: John Youn
From: Razmik Karapetyan
Check the request length in dwc2_hsotg_start_req() function. If
length == 0, do not write DMA address to control register.
Signed-off-by: Razmik Karapetyan
Signed-off-by: John Youn
---
This series includes some minor fixes and cleanup commits for dwc2
that we've had locally for some time.
Razmik Karapetyan (5):
usb: dwc2: Don't program DMA address for 0 length request
usb: dwc2: Fix Control Write issue in DMA mode
usb: dwc2: Remove unnecessary request length checking
From: Razmik Karapetyan
While sending zlp for DWC2_EP0_STATUS_IN EP direction was changed to IN.
Change it back to complete OUT transfer request.
This affects only on DMA mode, because DMA buffer map/unmap function is
direction sensitive.
Signed-off-by: Razmik Karapetyan
From: Sevak Arakelyan
Stop sending complete split requests in case of ISOC IN split transfers
after getting data with PID0. Otherwise we will get a NYET for each
additional IN token.
Signed-off-by: Sevak Arakelyan
Signed-off-by: John Youn
Use the new ahb_burst (instead of ahbcfg) to program the GAHBCFG.HBSTLEN
in both host and gadget mode.
Signed-off-by: John Youn
---
drivers/usb/dwc2/gadget.c | 2 +-
drivers/usb/dwc2/hcd.c| 8 +++-
drivers/usb/dwc2/params.c | 10 --
3 files changed, 4
Add the "snps,ahb-burst" binding and read it in.
This property controls which burst type to perform on the AHB bus as a
master in internal DMA mode. This overrides the legacy param value,
which we need to keep around for now since several platforms use it.
Some platforms may see better or worse
The BCM2835 has an alternate function for the GAHBCFG.HBSTLEN field.
Document this difference in the code.
Cc: Stefan Wahren
Signed-off-by: John Youn
---
drivers/usb/dwc2/params.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
This series adds a binding for AHB burst, reads it in, and configures
the controller for the specified burst type.
Tested on HAPS platform with DWC_hsotg IP version 3.30a.
v2:
* Don't remove the bcm2835 ahbcfg param and document why.
John Youn (4):
usb: dwc2: Document the AHB burst value for
Set the AHB burst to INCR for HAPS.
Signed-off-by: John Youn
---
drivers/usb/dwc2/pci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc2/pci.c b/drivers/usb/dwc2/pci.c
index a23329e..146b7ce 100644
--- a/drivers/usb/dwc2/pci.c
+++
On Wed, Nov 16, 2016 at 04:07:57PM +0100, Wim Osterholt wrote:
> A bit of patience please. Yesterday I hadn't the modem at hand.
Whell, I lost track of what happens where with which config file..
Confusion about the bug not appearing an too many configs with SMP set
where I'm sure the machine(s)
Francois Romieu [mailto:rom...@fr.zoreil.com]
> Sent: Tuesday, November 15, 2016 9:11 AM
[...]
> If it was possible to get it wrong once, it should be possible to
> get it wrong twice, especially if some part of the hardware design
> is recycled. I don't mean anything else.
I agree with you.
On Thu, Nov 17 2016, Mark Brown wrote:
> [ Unknown signature status ]
> On Tue, Nov 15, 2016 at 08:35:13AM +1100, NeilBrown wrote:
>> On Mon, Nov 14 2016, Mark Brown wrote:
>
>> > Conflating the two seems like the whole point here. We're looking for
>> > something that sits between the power
On Wed, Nov 16, 2016 at 01:21:21PM -0600, Bin Liu wrote:
> Hi Greg,
>
> Hope this is not too late for -rc6. This set fixes a long standing musb
> regression introduced in v4.8. Please let me know if any change is needed.
As these were bugs in 4.8 (i.e. not a regression due to changes in
On 2016-11-17 03:57, Oliver Neukum wrote:
On Wed, 2016-11-16 at 11:49 -0600, Dan Williams wrote:
This will make option grab all the ports, as shown by your dmesg
output. But USB interfaces 0 and 1 are actually cdc-ether and should
*not* be grabbed by option.
You want to limit option to
[...]
> Fix the hw rx checksum is always enabled, and the user couldn't switch
> it to sw rx checksum.
>
> Note that the RTL_VER_01 only supports sw rx checksum only. Besides,
> the hw rx checksum for RTL_VER_02 is disabled after
> commit b9a321b48af4 ("r8152: Fix broken RX checksums.").
On 11/16/2016 05:33 AM, Sriram Dash wrote:
>> From: Scott Wood
>> On 11/15/2016 06:39 AM, Sriram Dash wrote:
From: Scott Wood
On 11/13/2016 11:27 PM, Sriram Dash wrote:
> diff --git
> a/Documentation/devicetree/bindings/phy/phy-qoriq-usb3.txt
>
On 2016-11-17 01:35, Dan Williams wrote:
Also, is it really a D-Link DWM-158? That appears to be a USB dongle-
type device, while what's in the DWR-512 is a PCI-E minicard that looks
like a ZTE MF210, from the FCC pictures.
DWR-512A1 uses the ZTE MF210 module while DWR-512B1 uses the D-Link
On Wed, Nov 16, 2016 at 6:56 PM, Kai-Heng Feng
wrote:
> On Wed, Nov 16, 2016 at 6:47 PM, Greg KH wrote:
>> On Wed, Nov 16, 2016 at 06:42:27PM +0800, Kai-Heng Feng wrote:
>>> Originally I sent a not-working patch to the mailing list [1], turns
>>> out
On Wed, Nov 16, 2016 at 09:46:29PM +0100, Felix Hädicke wrote:
> Add check for NULL before calling kthread_stop().
>
> There were cases in which gserial_console_exit() was called, but the
> console thread was not started. This resulted in an invalid
> kthread_stop(NULL) call.
You can add oops
>From: Rob Herring [mailto:r...@kernel.org]
>On Mon, Nov 14, 2016 at 10:56:54AM +0530, Sriram Dash wrote:
>> Adds qoriq usb 3.0 phy driver support for LS1043A platform.
>> Describes the qoriq usb 2.0 phy driver binding, currently used for
>> LS1043A platform.
>>
>> Signed-off-by: Sriram Dash
On Wed, 2016-11-16 at 10:22 +0700, Lars Melin wrote:
> On 2016-11-16 03:20, Giuseppe Lippolis wrote:
> > Signed-off-by: Giuseppe Lippolis
> > ---
> > Adding support for 3G modem DWR-158 from Dlink (I found it embedded in the
> > DWR-512).
> > ---
> >
> > ---
Hi,
Greg KH writes:
> On Wed, Nov 16, 2016 at 12:12:53AM +0530, PrasannaKumar Muralidharan wrote:
>> >> scripts/kconfig/conf --silentoldconfig Kconfig
>> >> CHK include/config/kernel.release
>> >> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
On Tue, Nov 15, 2016 at 04:19:10PM -0800, Badhri Jagan Sridharan wrote:
> Hi,
>
> At present I am using the uevent in the userspace to infer
> the Presence of a port on the remote end through the
> appearance of usbc*-partner.
>
> Userspace uses this info to decide on when to show a USB
>
Hi,
Peter Chen writes:
> On Tue, Nov 15, 2016 at 10:54:09PM -0500, David Miller wrote:
>> From: Peter Chen
>> Date: Wed, 16 Nov 2016 11:41:15 +0800
>>
>> > I just notice that you submitted the "usb: gadget: u_ether: remove
>> > interrupt
On Wed, 2016-11-16 at 11:30 +0200, Heikki Krogerus wrote:
> On Tue, Nov 15, 2016 at 04:19:10PM -0800, Badhri Jagan Sridharan wrote:
> > Is that too costly to have ?
>
> Greg, could you give your opinion. In this case we do have attribute
> files that the user space can poll. Data role is the USB
Current abort operation has race.
xhci_handle_command_timeout()
xhci_abort_cmd_ring()
xhci_write_64(CMD_RING_ABORT)
xhci_handshake(5s)
do {
check CMD_RING_RUNNING
udelay(1)
...
Клиентские базы Skype: prodawez390 Whatsapp: +79139230330 Viber: +79139230330
Telegram: +79139230330 Email: prodawez...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi USB devs,
I have no idea who to contact for this, the bug predates git.
drivers/usb/host/ohci-pxa27x.c:150 pxa27x_ohci_select_pmm()
warn: odd binop '0x200 & 0x100'
drivers/usb/host/ohci-pxa27x.c
130 /*
131PMM_NPS_MODE -- PMM Non-power switching mode
132
On Mon, Nov 14, 2016 at 03:41:02PM +0100, Axel Haslam wrote:
> This patch documents the device tree bindings required for
> the ohci controller found in TI da8xx family of SoC's
>
> Cc: robh...@kernel.org
> Cc: mark.rutl...@arm.com
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Axel Haslam
Hi John,
> John Youn hat am 16. November 2016 um 01:36
> geschrieben:
>
>
> The ahbcfg param for bcm2835 is specifying a HBSTLEN of 0x8 (0x10 >> 1)
> which is not a valid value for that field. Remove the param and default
> to using INCR4.
i don't have any Synopsys
Hi,
John Youn writes:
> On 11/14/2016 3:00 PM, John Youn wrote:
>> On 11/11/2016 3:12 PM, Christian Lamparter wrote:
>>> On Friday, November 11, 2016 2:20:42 PM CET John Youn wrote:
On 11/11/2016 2:05 PM, Christian Lamparter wrote:
> On Friday, November 11,
On Wed, Nov 16, 2016 at 11:30:35AM +0200, Heikki Krogerus wrote:
> On Tue, Nov 15, 2016 at 04:19:10PM -0800, Badhri Jagan Sridharan wrote:
> > Hi,
> >
> > At present I am using the uevent in the userspace to infer
> > the Presence of a port on the remote end through the
> > appearance of
On Mon, 2016-11-14 at 06:34 -0800, Guenter Roeck wrote:
> >>> +int typec_connect(struct typec_port *port, struct
> typec_connection *con)
> >>> +{
> >>> + int ret;
> >>> +
> >>> + if (!con->partner && !con->cable)
> >>> + return -EINVAL;
> >>> +
> >>> + port->connected = 1;
> >>> +
Hi,
OGAWA Hirofumi writes:
> diff -puN drivers/usb/host/xhci-ring.c~xhci-fix-abort-race2
> drivers/usb/host/xhci-ring.c
> --- xhci/drivers/usb/host/xhci-ring.c~xhci-fix-abort-race22016-11-16
> 13:36:07.219329211 +0900
> +++
The BRIM Brothers Zone DPMX is a bicycle powermeter. This ID is for the
USB serial interface in its charging dock for the control pods, via
which some settings for the pods can be modified.
Signed-off-by: Paul Jakma
Cc: Barry Redmond
diff --git
On 11/15/2016 06:39 AM, Sriram Dash wrote:
>> From: Scott Wood
>> On 11/13/2016 11:27 PM, Sriram Dash wrote:
>>> diff --git a/Documentation/devicetree/bindings/phy/phy-qoriq-usb3.txt
>>> b/Documentation/devicetree/bindings/phy/phy-qoriq-usb3.txt
>>> new file mode 100644
>>> index 000..d934c80
On 2016-11-16 15:53, Oliver Neukum wrote:
On Wed, 2016-11-16 at 10:22 +0700, Lars Melin wrote:
On 2016-11-16 03:20, Giuseppe Lippolis wrote:
Signed-off-by: Giuseppe Lippolis
---
Adding support for 3G modem DWR-158 from Dlink (I found it embedded in the
DWR-512).
---
Felipe Balbi writes:
> Hi,
Hi,
> OGAWA Hirofumi writes:
>> diff -puN drivers/usb/host/xhci-ring.c~xhci-fix-abort-race2
>> drivers/usb/host/xhci-ring.c
>> --- xhci/drivers/usb/host/xhci-ring.c~xhci-fix-abort-race2 2016-11-16
>>
Hi Bjørn,
2016-11-15 19:56 GMT+01:00 Bjørn Mork :
> Daniele Palmas writes:
>
>> The problem is in cdc_ncm, function cdc_ncm_bind_common, line
>>
>> usleep_range(1, 2);
>>
>> It seems that LE922 needs an higher timeout; changing the line to
>>
>>
On Wed, Nov 16, 2016 at 6:47 PM, Greg KH wrote:
> On Wed, Nov 16, 2016 at 06:42:27PM +0800, Kai-Heng Feng wrote:
>> Originally I sent a not-working patch to the mailing list [1], turns
>> out the patch is far from correct.
>>
>> Bjørn Mork suggests that we can cover the USB3 pair
On 11/15/2016 11:46 AM, Sekhar Nori wrote:
> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>> This adds the device tree node for the usb otg
>> controller present in the da850 family of SoC's.
>> This also enables the otg usb controller for the lcdk board.
>>
>> Signed-off-by:
From: Petr Kulhavy
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy
Acked-by: Sergei Shtylyov
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
Changes in v2:
* Remove unrelated changes in patch 3
* Rename the device node in patch 4
Changes in v3:
* Fix few mistakes in DT binding sample
* Only build the device table if DT is enabled
Change in v4:
* Fix a nit
Changes in v5:
* Nothing. Resent the v4 in two seppaated series: one for
On Mon, Nov 14, 2016 at 3:34 PM, Kai-Heng Feng
wrote:
> On Fri, Nov 11, 2016 at 10:44 PM, Mathias Nyman
> wrote:
>> On 10.11.2016 13:22, Oliver Neukum wrote:
>>>
>>> On Thu, 2016-11-10 at 12:09 +0100, Bjørn Mork wrote:
From: Petr Kulhavy
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
---
drivers/usb/musb/da8xx.c | 46
From: Petr Kulhavy
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/da8xx-usb.txt
On Wed, 2016-11-16 at 13:09 +0200, Heikki Krogerus wrote:
> OK, I'll add KOBJ_CHANGE for those.
>
> So is it OK to everybody if I remove the KOBJ_CHANGE in
> typec_connect()? We will see uevent KOBJ_ADD since the partner (or
> cable) is added in any case. Badhri, Oliver?
OK by me.
USB-3 does not have any link state that will avoid negotiating a connection
with a plugged-in cable but will signal the host when the cable is
unplugged.
For USB-3 we used to first set the link to Disabled, then to RxDdetect to
be able to detect cable connects or disconnects. But in RxDetect the
On Wed, Nov 16, 2016 at 06:42:27PM +0800, Kai-Heng Feng wrote:
> Originally I sent a not-working patch to the mailing list [1], turns
> out the patch is far from correct.
>
> Bjørn Mork suggests that we can cover the USB3 pair diff pins with
> tape to do some experiment, but the vendor told me
On 11/16/2016 11:41 AM, Sekhar Nori wrote:
> On Wednesday 16 November 2016 04:05 PM, Alexandre Bailon wrote:
>> On 11/15/2016 11:46 AM, Sekhar Nori wrote:
>>> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
This adds the device tree node for the usb otg
controller present
Hi,
Sriram Dash writes:
> From: Arnd Bergmann
>
> The dma ops for dwc3 devices are not set properly. So, use a
> physical device sysdev, which will be inherited from parent,
> to set the hardware / firmware parameters like dma.
>
> Signed-off-by: Arnd
On Wednesday 16 November 2016 04:05 PM, Alexandre Bailon wrote:
> On 11/15/2016 11:46 AM, Sekhar Nori wrote:
>> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>>> This adds the device tree node for the usb otg
>>> controller present in the da850 family of SoC's.
>>> This also
This adds the device tree node for the usb otg
controller present in the da850 family of SoC's.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi
This add and enable the usb otg for da850 and da850-lcdk.
This series depends on "driver: dd DT support for DA8xx" patch set.
If this series is applied before the "usb: musb: da8xx: Fix few issues" patch
set then the usb driver will always retrun -ENODEV.
Changes in v2:
* Remove unrelated
This enables the usb otg controller for the lcdk board.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850-lcdk.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/da850-lcdk.dts b/arch/arm/boot/dts/da850-lcdk.dts
index
Hi,
Arnd Bergmann writes:
> A change to the suspend/resume handling in dwc3-pci introduced a
> harmless warning:
>
> drivers/usb/dwc3/dwc3-pci.c:169:12: error: ‘dwc3_pci_dsm’ defined but not
> used [-Werror=unused-function]
>
> Replacing the #ifdef around the PM functions with
On Wed, Nov 16, 2016 at 10:49:49AM +0100, Greg KH wrote:
> On Wed, Nov 16, 2016 at 11:30:35AM +0200, Heikki Krogerus wrote:
> > On Tue, Nov 15, 2016 at 04:19:10PM -0800, Badhri Jagan Sridharan wrote:
> > > Hi,
> > >
> > > At present I am using the uevent in the userspace to infer
> > > the
>From: Scott Wood
>On 11/15/2016 06:39 AM, Sriram Dash wrote:
>>> From: Scott Wood
>>> On 11/13/2016 11:27 PM, Sriram Dash wrote:
diff --git
a/Documentation/devicetree/bindings/phy/phy-qoriq-usb3.txt
b/Documentation/devicetree/bindings/phy/phy-qoriq-usb3.txt
new file mode
Hi Greg,
On Mon, Nov 14, 2016 at 10:51:48AM +0100, Greg KH wrote:
> > +static int sysfs_strmatch(const char * const *array, size_t n, const char
> > *str)
> > +{
> > + const char *item;
> > + int index;
> > +
> > + for (index = 0; index < n; index++) {
> > + item = array[index];
> Yes, though I don't KOBJ_ADD separately with the partners and cables.
> That uevent is sent when the device for them is registered, so it's
> already there
Makes sense. Thanks Heikki.
Regards,
Badhri
On Wed, Nov 16, 2016 at 7:20 AM, Heikki Krogerus
wrote:
>
> IMHO the uevent is cheaper. User space cannot just poll without further
> infrastructure. A task needs to run to poll. A uevent can be handled
> through established infrastructure.
Thanks Oliver for stating this. This is exactly what I was facing.
> OK, I'll add KOBJ_CHANGE for those.
>
> So
On Wed, Nov 16, 2016 at 06:30:23AM -0800, Badhri Jagan Sridharan wrote:
> > IMHO the uevent is cheaper. User space cannot just poll without further
> > infrastructure. A task needs to run to poll. A uevent can be handled
> > through established infrastructure.
>
> Thanks Oliver for stating this.
On 16.11.2016 11:50, OGAWA Hirofumi wrote:
Current abort operation has race.
xhci_handle_command_timeout()
xhci_abort_cmd_ring()
xhci_write_64(CMD_RING_ABORT)
xhci_handshake(5s)
do {
check CMD_RING_RUNNING
udelay(1)
On Wed, Nov 16, 2016 at 01:34:30PM +0100, Oliver Neukum wrote:
>
> This is very odd. We need to know where it crashes. Please try the
> insane debug patch I posted.
A bit of patience please. Yesterday I hadn't the modem at hand.
Groeten, Wim.
--
To unsubscribe from this list: send the line
* Sekhar Nori [161115 22:25]:
> On Wednesday 16 November 2016 02:28 AM, Tony Lindgren wrote:
> > * Sekhar Nori [161115 00:35]:
> >> If pm_runtime_get_sync() fails due to callback error, then
> >> rpm_callback() sets dev.power.runtime_error to an error value which
Building with W=1, we get a warning about harmless empty statements:
drivers/usb/dwc3/ep0.c: In function 'dwc3_ep0_handle_intf':
drivers/usb/dwc3/ep0.c:491:4: error: suggest braces around empty body in an
'if' statement [-Werror=empty-body]
gcc does not warn about {} here, so maybe use that
> At least Debian started building toolchains with PIE enabled by
> default. I've had this problem for a while, actually. I'm building
> kernels with:
>
> $ make CC="gcc -fno-PIE"
>
> and everything builds fine.
Great. Kernel build is going on now. Will post about further developments.
--
To
On Wednesday, November 16, 2016 1:17:51 PM CET Felipe Balbi wrote:
> dwc3_pci_dsm() is only needed if (PM || PM_SLEEP),
> we should make sure it's not defined if neither of
> those is defined.
>
> This fixes a randconfig build warning.
>
> Reported-by: Arnd Bergmann
>
On Wed, Nov 16, 2016 at 06:56:30PM +0800, Kai-Heng Feng wrote:
> On Wed, Nov 16, 2016 at 6:47 PM, Greg KH wrote:
> > On Wed, Nov 16, 2016 at 06:42:27PM +0800, Kai-Heng Feng wrote:
> >> Originally I sent a not-working patch to the mailing list [1], turns
> >> out the patch is far
On Wednesday, November 16, 2016 1:13:48 PM CET Felipe Balbi wrote:
> Arnd Bergmann writes:
> > A change to the suspend/resume handling in dwc3-pci introduced a
> > harmless warning:
> >
> > drivers/usb/dwc3/dwc3-pci.c:169:12: error: ‘dwc3_pci_dsm’ defined but not
> > used
On Wed, Nov 16, 2016 at 10:13:49AM +, Paul Jakma wrote:
> The BRIM Brothers Zone DPMX is a bicycle powermeter. This ID is for the
> USB serial interface in its charging dock for the control pods, via
> which some settings for the pods can be modified.
>
> Signed-off-by: Paul Jakma
On Tue, Nov 15, 2016 at 08:35:13AM +1100, NeilBrown wrote:
> On Mon, Nov 14 2016, Mark Brown wrote:
> > Conflating the two seems like the whole point here. We're looking for
> > something that sits between the power supply code and the USB code and
> > tells the power supply code what it's
On Wed, Nov 16, 2016 at 05:20:24PM +0200, Heikki Krogerus wrote:
> Hi Greg,
>
> On Mon, Nov 14, 2016 at 10:51:48AM +0100, Greg KH wrote:
> > > +static int sysfs_strmatch(const char * const *array, size_t n, const
> > > char *str)
> > > +{
> > > + const char *item;
> > > + int index;
> > > +
> >
Mathias Nyman writes:
> The retry was a workaround for a case triggered on v4.1.4 by
> Vincent Pelletier (added to CC)
>
>http://marc.info/?l=linux-usb=144031185222108=2
>
> The race could very well explain that issue.
>From logs of that thread, it would has
Current abort operation has race.
xhci_handle_command_timeout()
xhci_abort_cmd_ring()
xhci_write_64(CMD_RING_ABORT)
xhci_handshake(5s)
do {
check CMD_RING_RUNNING
udelay(1)
...
On Tue, 2016-11-15 at 14:29 +0100, Wim Osterholt wrote:
> I experience a sliding scale.
> With debug it crashes immediately. It may crash later on (even at shutdown
> time). It's not even an oops but a warning. In the end it happens to just
> work.
This is very odd. We need to know where it
On Tue, 2016-11-15 at 20:13 +0100, Giuseppe Lippolis wrote:
> Dear all,
> I'm porting the Dlink DWR-512 device to LEDE (embedded linux).
> This device embed a 3G modem connected through the usb bus .
> The modem work properly with the option kernel module.
>
> I added these line in the
>
>
On Wed, Nov 16, 2016 at 12:06:51PM +0530, Sekhar Nori wrote:
> On Wednesday 16 November 2016 02:49 AM, Bin Liu wrote:
> > On Tue, Nov 15, 2016 at 04:16:02PM +0530, Sekhar Nori wrote:
> >> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
> >>> This adds the device tree node for the
On Wednesday 16 November 2016 03:29 AM, Bin Liu wrote:
> On Tue, Nov 15, 2016 at 01:37:55PM -0800, Tony Lindgren wrote:
>> Now with musb driver implementing generic session bit based
>> PM, we need to have the USB PHYs behaving in a sane way for
>> platforms implementing PM.
>>
>> Currently
* Tony Lindgren [161116 06:55]:
> * Sekhar Nori [161115 22:25]:
> > On Wednesday 16 November 2016 02:28 AM, Tony Lindgren wrote:
> > > * Sekhar Nori [161115 00:35]:
> > >> If pm_runtime_get_sync() fails due to callback error, then
> > >>
1 - 100 of 104 matches
Mail list logo