Hi Manish,
(Added target-devel CC')
On Mon, 2017-03-20 at 15:05 +0530, Manish Narani wrote:
> This patch corrects the argument in usb_ep_free_request as it is
> mistakenly set to ep_out. It should be ep_in for status request.
>
> Signed-off-by: Manish Narani
> ---
> drivers/usb/gadget/function
Hi Elena,
On Mon, 2017-03-06 at 16:21 +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations
Hi Mathias,
On 21 February 2017 at 10:09, Baolin Wang wrote:
>> Do you have any comments about this patch? Thanks.
>>
>>>drivers/usb/host/xhci-plat.c | 41
>>> -
>>>1 file changed, 36 insertions(+), 5 deletions(-)
>>>
>>
Hi,
On 03/20/2017 10:41 PM, Andy Shevchenko wrote:
> There is a so called ACPI support for extcon-usb-gpio.
>
> Since GPIO ACPI library is going to be stricter and this driver might
> not work anymore.
>
> I would like to know:
> 1. Is there any real DSDT which contains device enumerated by this
>
XHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. Software
learns this capability by walking through the extended
capability list of the host. XHCI specification describes
DbC in the section 7.6.
This patch introduces the code to probe and
This patch adds dbc debug device support to the usb_debug driver.
Signed-off-by: Lu Baolu
Acked-by: Johan Hovold
---
drivers/usb/serial/usb_debug.c | 28 +---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/usb_debug.c b/drivers/usb/seri
Add a simple udelay calibration in x86 architecture-specific
boot-time initializations. This will get a workable estimate
for loops_per_jiffy. Hence, udelay() could be used after this
initialization.
Cc: Ingo Molnar
Cc: x...@kernel.org
Signed-off-by: Lu Baolu
---
arch/x86/kernel/setup.c | 22 ++
Add Documentation/usb/usb3-debug-port.rst. This document includes
the guide for using USB3 debug port.
Cc: linux-...@vger.kernel.org
Signed-off-by: Lu Baolu
---
Documentation/usb/usb3-debug-port.rst | 100 ++
1 file changed, 100 insertions(+)
create mode 100644 D
Add support for earlyprintk by writing debug messages to the
USB3 debug port. Users can use this type of early printk by
specifying the kernel parameter of "earlyprintk=xdbc". This
gives users a chance of providing debugging output.
The hardware for USB3 debug port requires DMA memory blocks.
This
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. With DbC
hardware initialized, the system will present a debug device
through the USB3 debug port (normally the first USB3 port).
The debug device is fully compliant with the USB framework
a
Hi,
Baolin Wang writes:
>>> I don't yet understand why we can't just keep runtime pm disabled as a
>>> default for xhci platform devices.
>>> It could be enabled by whatever creates the platform device by setting some
>>> device property
>>> (or equivalent), which would be checked in xhci_plat_p
On Tue, Feb 21, 2017 at 05:24:02PM +0300, Heikki Krogerus wrote:
> The USB Type-C class is meant to provide unified interface to the
> userspace to present the USB Type-C ports in a system.
>
> Changes since v16:
> - Using PTR_ERR_OR_ZERO macro in typec_init().
I'm lost in the long thread here, i
On Tue, Mar 21, 2017 at 11:23:37AM +0100, Greg KH wrote:
> On Tue, Feb 21, 2017 at 05:24:02PM +0300, Heikki Krogerus wrote:
> > The USB Type-C class is meant to provide unified interface to the
> > userspace to present the USB Type-C ports in a system.
> >
> > Changes since v16:
> > - Using PTR_ER
On Tue, Feb 21, 2017 at 05:42:35PM +0200, Felipe Balbi wrote:
> Just to clarify one thing here: wherever it says "Reviewed-by: Felipe
> Balbi..." you could also read "Reviewed-and-Tested-by: Felipe Balbi..."
> as I have been running these patches for past few months to test code on
> Intel Joule.
Am Donnerstag, den 16.03.2017, 23:18 +0100 schrieb Philippe Reynes:
> The ethtool api {get|set}_settings is deprecated.
> We add the new api {get|set}_link_ksettings to this driver.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
Unfortunately I lack har
* Lu Baolu wrote:
> xHCI debug capability (DbC) is an optional but standalone
> functionality provided by an xHCI host controller. With DbC
> hardware initialized, the system will present a debug device
> through the USB3 debug port (normally the first USB3 port).
> The debug device is fully com
This adds driver for the USB Type-C PHY on Intel WhiskeyCove
PMIC which is available on some of the Intel Broxton SoC
based platforms.
Signed-off-by: Heikki Krogerus
Reviewed-by: Mika Westerberg
Reviewed-and-Tested-by: Felipe Balbi
Tested-by: Guenter Roeck
---
drivers/usb/typec/Kconfig
The USB Type-C class is meant to provide unified interface to the
userspace to present the USB Type-C ports in a system.
Changes since v17:
- Small documentation improvements.
Changes since v16:
- Using PTR_ERR_OR_ZERO macro in typec_init().
Changes since v15:
- "stingification" as proposed by
Make a simple helper for matching strings with sysfs
attribute files. In most parts the same as match_string(),
except sysfs_match_string() uses sysfs_streq() instead of
strcmp() for matching. This is more convenient when used
with sysfs attributes.
Signed-off-by: Heikki Krogerus
Reviewed-by: Mik
The purpose of USB Type-C connector class is to provide
unified interface for the user space to get the status and
basic information about USB Type-C connectors on a system,
control over data role swapping, and when the port supports
USB Power Delivery, also control over power role swapping
and Alt
On Tue, Mar 21, 2017 at 12:33:28PM +0100, Ingo Molnar wrote:
>
> * Lu Baolu wrote:
>
> > xHCI debug capability (DbC) is an optional but standalone
> > functionality provided by an xHCI host controller. With DbC
> > hardware initialized, the system will present a debug device
> > through the USB3
* Greg Kroah-Hartman wrote:
> > I've applied them locally to -tip (it appears the USB maintainers are still
> > fine with this being carried in tip:x86/debug for a v4.12 merge, right?),
> > and
> > will push them out and will propagate them to linux-next as well if they
> > pass
> > testing
On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
>> wrote:
>>> On 20.03.2017 17:39, Diego Viola wrote:
On Mon, Mar 20, 2017 at 11:21 AM, Mathias Nyman
wrote:
>
> On
On Sun, Mar 19, 2017 at 03:30:38PM -0700, Florian Fainelli wrote:
> Le 03/19/17 à 03:59, Russell King - ARM Linux a écrit :
> > This series of patches does exactly that - we merge the functionality
> > of the indirect accesses into the clause 45 accessors, and use these
> > exclusively to access MM
On Wed, 8 Mar 2017, Benjamin Tissoires wrote:
> It looks like a bunch of devices do not like to be polled for their
> reports at init time. When you look into the details, it seems that for
> those that are requiring the quirk HID_QUIRK_NO_INIT_REPORTS, the driver
> fails to retrieve part of th
On Fri, 3 Mar 2017, Jaejoong Kim wrote:
> Jaejoong Kim (2):
> HID: cp2112: use proper hidraw name with minor number
> HID: hiddev: reallocate hiddev's minor number
Applied to for-4.12/hiddev. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linu
On 16.03.2017 23:18, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
> ---
> drivers/n
> Thanks. When I posted this last time around (19th Jan) I mentioned
> about marking the old _indirect() accessors with __deprecated - is
> that still something we want to do?
>
> I haven't tested this against net-next yet, so I don't know if there
> are any new users of the indirect accessors -
On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote:
> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
>>> On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
>>> wrote:
On 20.03.2017 17:39, Diego Viola wrote:
>
> On Mon, Mar 20
On Mon, 20 Mar 2017, Gerd Hoffmann wrote:
> On a loaded virtualization host (dozen guests booting at the same time)
> it may happen that the ohci controller emulation doesn't manage to do
> timely frame processing, with the result that the io watchdog fires and
> considers the controller being dea
Make phy_(read|write)_mmd() generic 802.3 clause 45 register accessors
for both Clause 22 and Clause 45 PHYs, using either the direct register
reading for Clause 45, or the indirect method for Clause 22 PHYs.
Allow this behaviour to be overriden by PHY drivers where necessary.
Reviewed-by: Andrew
This series cleans up phylib's MMD accessors, so that we have a common
way of accessing the Clause 45 register set.
The current situation is far from ideal - we have phy_(read|write)_mmd()
which accesses Clause 45 registers over Clause 45 accesses, and we have
phy_(read|write)_mmd_indirect(), whic
Convert micrel to the new read_mmd/write_mmd driver methods. This
Clause 22 PHY does not support any MMD access method.
Reviewed-by: Andrew Lunn
Reviewed-by: Florian Fainelli
Signed-off-by: Russell King
---
drivers/net/phy/micrel.c | 13 ++---
1 file changed, 6 insertions(+), 7 deleti
lan78xx appears to use phylib in a rather weird way, accessing the PHY
partly through phylib, and partly by making direct accesses to it,
including to the Clause 45 registers. As the indirect MMD accessors are
going away, update this driver to use the plain phy_(read|write)_mmd()
accessors instead
Move the phy_(read|write)__mmd() helpers out of line, they will become
our main MMD accessor functions, and so will be a little more complex.
This complexity doesn't belong in an inline function. Also move the
_indirect variants as well to keep like functionality together.
Reviewed-by: Andrew Lun
Switch everyone over to using phy_read_mmd() and phy_write_mmd() now
that they are able to handle both Clause 22 indirect addressing and
Clause 45 direct addressing methods to the MMD registers.
Reviewed-by: Andrew Lunn
Reviewed-by: Florian Fainelli
Signed-off-by: Russell King
---
drivers/net/
Make mmd_phy_indirect() use the same terminology as the rest of the
code, making clear what each address is - phy address, devad, and
register number.
While here, remove the "inline" from this static function, leaving
it to the compiler to decide whether to inline this function, and
get rid of unn
Remove the indirect MMD read/write methods which are now no longer
necessary.
Reviewed-by: Andrew Lunn
Reviewed-by: Florian Fainelli
Signed-off-by: Russell King
---
drivers/net/phy/phy-core.c | 119 +
include/linux/phy.h| 42
From: Hayes Wang
Date: Tue, 14 Mar 2017 14:15:20 +0800
> The list rx_done would be initialized when the linking on occurs.
> Therefore, if a napi is scheduled without any linking on before,
> the following kernel panic would happen.
>
> BUG: unable to handle kernel NULL pointer dereference
On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola wrote:
> On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote:
>> On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola wrote:
>>> On Mon, Mar 20, 2017 at 3:27 PM, Diego Viola wrote:
On Mon, Mar 20, 2017 at 1:32 PM, Mathias Nyman
wrote:
> On 20
From: Philippe Reynes
Date: Thu, 16 Mar 2017 23:18:46 +0100
> The ethtool api {get|set}_settings is deprecated. On usbnet, it
> was often implemented with usbnet_{get|set}_settings.
>
> In this serie, I add usbnet_{get|set}_link_ksettings
> in the first patch, then I update all the driver to
> u
From: Oliver Neukum
Date: Tue, 21 Mar 2017 12:33:03 +0100
> Am Donnerstag, den 16.03.2017, 23:18 +0100 schrieb Philippe Reynes:
>> The ethtool api {get|set}_settings is deprecated.
>> We add the new api {get|set}_link_ksettings to this driver.
>>
>> As I don't have the hardware, I'd be very plea
From: Hayes Wang
Date: Fri, 17 Mar 2017 11:20:13 +0800
> Check hw version first in probe(). Do nothing if the driver doesn't
> support the chip.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to ma
From: Bjørn Mork
Date: Fri, 17 Mar 2017 17:20:48 +0100
> This is a Dell branded Sierra Wireless EM7455. It is operating in
> MBIM mode by default, but can be configured to provide two QMI/RMNET
> functions.
>
> Signed-off-by: Bjørn Mork
> ---
> Note regarding stable backports:
>
> This device
Hi,
On Thu, Mar 16, 2017 at 08:51:52PM -0700, Tony Lindgren wrote:
> Some Motorola phones like droid 4 use a custom CPCAP PMIC that has a
> multiplexing USB PHY.
>
> This USB PHY can operate at least in four modes using pin multiplexing
> and two control GPIOS:
>
> - Pass through companion PHY f
Hi,
On 03/21/2017 07:33 PM, Ingo Molnar wrote:
>> Lu Baolu (5):
>> > x86: add simple udelay calibration
>> > usb: early: add driver for xhci debug capability
>> > x86: add support for earlyprintk via USB3 debug port
>> > usb: serial: add dbc debug device support to usb_debug
>> > usb: do
Hi,
On 21 March 2017 at 16:07, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
I don't yet understand why we can't just keep runtime pm disabled as a
default for xhci platform devices.
It could be enabled by whatever creates the platform device by setting some
device prop
Greg, hope you had not faced any issue (tab converted to spaces) with this
patch.
In case still facing any issue please let me know.
> There is race condition when two USB class drivers try to call
> init_usb_class at the same time and leads to crash.
> code path: probe->usb_register_dev->init_u
On 03/20, Baolin Wang wrote:
>Hi,
>
>
>On 19 March 2017 at 19:42, kbuild test robot wrote:
>> Hi Baolin,
>>
>> [auto build test ERROR on balbi-usb/next]
>> [also build test ERROR on v4.11-rc2 next-20170310]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help impro
Hi,
On 22 March 2017 at 14:32, Ye Xiaolong wrote:
> On 03/20, Baolin Wang wrote:
>>Hi,
>>
>>
>>On 19 March 2017 at 19:42, kbuild test robot wrote:
>>> Hi Baolin,
>>>
>>> [auto build test ERROR on balbi-usb/next]
>>> [also build test ERROR on v4.11-rc2 next-20170310]
>>> [if your patch is applied
50 matches
Mail list logo
