From: Stephen Hemminger
Date: Thu, 31 Aug 2017 16:16:11 -0700
> The first gets rid of unnecessary ref counting, and second
> allows removing hv_netvsc driver even if VF present.
Series applied.
___
devel mailing list
> -Original Message-
> From: Colin King [mailto:colin.k...@canonical.com]
> Sent: Friday, September 1, 2017 6:08 AM
> To: Greg Kroah-Hartman ; Sell, Timothy C
> ; Binder, David Anthony
> ; Wadgaonkar, Sameer
We need to add mappings for the mux subsys to be able to find the
muxes for the fusb302 driver to be able to control the PI3USB30532
Type-C mux and the device/host mux integrated in the CHT SoC.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/Kconfig | 1
So far the mux functionality of the tcpm code has not been hooked up
in any tcpc drivers. This commit adds a generic TCPC mux driver using
the mux subsys, which tcpc drivers can use to provide mux functionality
in cases where an external my is used.
Signed-off-by: Hans de Goede
Setting the mux to TYPEC_MUX_NONE, TCPC_USB_SWITCH_DISCONNECT when the
data-role is device is not correct. Plenty of devices support operating
as USB device through a (separate) USB device controller.
So this commit instead splits out TYPEC_MUX_USB into TYPEC_MUX_USB_HOST
and TYPEC_MUX_USB_DEVICE
Add mux support to the fusb302 driver, call devm_tcpc_gen_mux_create()
to let the generic tcpc_mux_dev code create a tcpc_mux_dev for us.
Also document the mux-names used by the generic tcpc_mux_dev code in
our devicetree bindings.
Cc: Rob Herring
Cc: Mark Rutland
Intel Cherrytrail SoCs have an internal USB mux for muxing the otg-port
USB data lines between the xHCI host controller and the dwc3 gadget
controller. On some Cherrytrail systems this mux is controlled through
AML code reacting on a GPIO IRQ connected to the USB OTG id pin (through
an _AIE ACPI
Add a driver for the Pericom PI3USB30532 Type-C cross switch /
mux chip found on some devices with a Type-C port.
Signed-off-by: Hans de Goede
---
drivers/mux/Kconfig | 10 +
drivers/mux/Makefile | 2 +
drivers/mux/pi3usb30532.c | 97
Hi All,
This series consists of 4 parts:
1) Core mux changes to add support for getting mux-controllers on
non DT platforms and to add some standardised state values for USB
2) Add Intel CHT USB mux and Pericom-PI3USB30532 Type-C mux drivers
3) Hookup the Intel CHT USB mux driver for CHT
On non DT platforms we cannot get the mux_chip by pnode. Other subsystems
(regulator, clock, pwm) have the same problem and solve this by allowing
platform / board-setup code to add entries to a lookup table and then use
this table to look things up.
This commit adds support for getting a mux
Cherry Trail SoCs have a built-in USB-role mux for switching between
the host and device controllers, rather then using an external mux
controller by a GPIO.
There is a driver using the mux-subsys to control this mux, this
commit adds support to the intel-int3496 driver to get a mux_controller
The Intel cherrytrail xhci controller has an extended cap mmio-range
which contains registers to control the muxing to the xhci (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a mux driver included in the xhci code (or under drivers/usb/host)
is not desirable.
Add MUX_USB_* state constant defines, which can be used by USB
device/host and Type-C polarity/role/altmode mux drivers and consumers
to ensure that they agree on the meaning of the mux_control_select()
state argument.
Signed-off-by: Hans de Goede
---
Currently the mux_control_get implementation only deals with getting
mux controllers on DT platforms. This commit renames the current
implementation to of_mux_control_get to reflect this and makes
mux_control_get a wrapper around of_mux_control_get.
This is a preparation patch for adding support
On 08/31/2017 05:29 PM, Kees Cook wrote:
> Several timer users needlessly reset their .function/.data fields during
> their timer callback, but nothing else changes them. Some users do not
> use their .data field at all. Each instance is removed here.
For amiflop:
Acked-by: Jens Axboe
Kees Cook writes:
> Several timer users needlessly reset their .function/.data fields during
> their timer callback, but nothing else changes them. Some users do not
> use their .data field at all. Each instance is removed here.
For *wan/hdlc*
Acked-by: Krzysztof Halasa
On Fri, Sep 1, 2017 at 2:38 AM, Ian Abbott wrote:
> On 01/09/17 10:29, Ian Abbott wrote:
>>
>> On 01/09/17 00:29, Kees Cook wrote:
>>>
>>> With timer initialization made unconditional, there is no reason to
>>> make del_timer_sync() calls conditionally, there by removing the
On Fri, Sep 01, 2017 at 06:08:48PM +0100, Martyn Welch wrote:
> The following changes since commit 0f9b011d3321ca1079c7a46c18cb1956fbdb7bcb:
>
> driver core: bus: Fix a potential double free (2017-08-31 18:57:30 +0200)
>
> are available in the git repository at:
>
>
The following changes since commit 0f9b011d3321ca1079c7a46c18cb1956fbdb7bcb:
driver core: bus: Fix a potential double free (2017-08-31 18:57:30 +0200)
are available in the git repository at:
https://gitlab.collabora.com/martyn/linux.git tags/vme-next-4.13-rc7
for you to fetch changes up to
On Fri, Sep 01, 2017 at 12:40:59PM +0530, Janani Sankara Babu wrote:
> This patch is created to solve the CamelCase issue. The members 'IEs'
> and 'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
> 'ie_length' to solve the issue. And the places where these variables
> are
On Fri, Sep 01, 2017 at 11:20:57AM +0100, Colin King wrote:
> From: Colin Ian King
>
> The const structure fusb302_psy_desc is local to the source and
> does not need to be in global scope, so make it static.
>
> Cleans up sparse warnings
> symbol 'fusb302_psy_desc'
On Fri, Sep 01, 2017 at 01:02:32PM +, Horia Geantă wrote:
> On 9/1/2017 11:30 AM, Greg Kroah-Hartman wrote:
> > On Fri, Sep 01, 2017 at 08:14:16AM +, Horia Geantă wrote:
> >> On 8/31/2017 7:20 PM, Greg Kroah-Hartman wrote:
> >>> On Wed, Aug 30, 2017 at 01:41:58PM +0300, Horia Geantă wrote:
There is a common for x86 IOSF MBI API. Move atomisp code to use it.
Signed-off-by: Andy Shevchenko
---
drivers/staging/media/atomisp/pci/Kconfig | 1 +
.../media/atomisp/pci/atomisp2/atomisp_cmd.c | 20 +++-
intel_mid_soc_stepping() is not used anywhere.
Signed-off-by: Andy Shevchenko
---
drivers/staging/media/atomisp/include/asm/intel_mid_pcihelpers.h | 1 -
.../media/atomisp/platform/intel-mid/intel_mid_pcihelpers.c| 7 ---
2 files changed, 8
In many files in the driver the intel-mid.h header inclusion is redundant.
Signed-off-by: Andy Shevchenko
---
drivers/staging/media/atomisp/i2c/imx/drv201.c| 1 -
drivers/staging/media/atomisp/i2c/imx/dw9714.c| 1
Since we switched to upstream IOSF MBI API the custom code become not in
use anymore.
Signed-off-by: Andy Shevchenko
---
.../atomisp/include/asm/intel_mid_pcihelpers.h | 22 -
.../media/atomisp/pci/atomisp2/atomisp_internal.h | 1 -
Remove dead code. If someone needs it the P-Unit semaphore is handled by
I2C DesignWare driver (drivers/i2c/busses/i2c-designware-baytrail.c).
Signed-off-by: Andy Shevchenko
---
.../atomisp/include/asm/intel_mid_pcihelpers.h | 2 -
intel_mid_msgbus_*_raw*() are not used anywhere.
Signed-off-by: Andy Shevchenko
---
.../atomisp/include/asm/intel_mid_pcihelpers.h | 4 --
.../platform/intel-mid/intel_mid_pcihelpers.c | 58 --
2 files changed, 62 deletions(-)
The d3_delay parameter is set by arch/x86/pci/intel_mid_pci.c and
drivers/pci/quirks.c.
No need to override that settings in unrelated driver.
Signed-off-by: Andy Shevchenko
---
.../atomisp/include/asm/intel_mid_pcihelpers.h | 8 --
On 9/1/2017 11:30 AM, Greg Kroah-Hartman wrote:
> On Fri, Sep 01, 2017 at 08:14:16AM +, Horia Geantă wrote:
>> On 8/31/2017 7:20 PM, Greg Kroah-Hartman wrote:
>>> On Wed, Aug 30, 2017 at 01:41:58PM +0300, Horia Geantă wrote:
This patch set adds support for functionalities needed by the
Fix the values of DPAA2_FD_CTRL_FSE and DPAA2_FD_CTRL_FAERR,
which are shifted off by one bit.
Fixes: 39163c0ce0f48 ("staging: fsl-dpaa2/eth: Errors checking update")
Cc:
Signed-off-by: Horia Geantă
---
On Fri, 2017-09-01 at 11:08 +0100, Colin King wrote:
> From: Colin Ian King
>
> The functions sig_queue_offset and sig_data_offset are local to
> the source and do not need to be in global scope, so make them
> static.
>
> Cleans up sparse warnings:
> symbol
From: Colin Ian King
The const structure fusb302_psy_desc is local to the source and
does not need to be in global scope, so make it static.
Cleans up sparse warnings
symbol 'fusb302_psy_desc' was not declared. Should it be static?
Signed-off-by: Colin Ian King
From: Colin Ian King
The functions sig_queue_offset and sig_data_offset are local to
the source and do not need to be in global scope, so make them
static.
Cleans up sparse warnings:
symbol 'sig_queue_offset' was not declared. Should it be static?
symbol
On 01/09/17 10:29, Ian Abbott wrote:
On 01/09/17 00:29, Kees Cook wrote:
With timer initialization made unconditional, there is no reason to
make del_timer_sync() calls conditionally, there by removing the test
of the .data field.
Cc: Ian Abbott
Cc: H Hartley Sweeten
On 01/09/17 00:29, Kees Cook wrote:
With timer initialization made unconditional, there is no reason to
make del_timer_sync() calls conditionally, there by removing the test
of the .data field.
Cc: Ian Abbott
Cc: H Hartley Sweeten
Cc: Greg
On Fri, Sep 01, 2017 at 09:58:52AM +0100, Piotr Gregor wrote:
> On Fri, Sep 01, 2017 at 08:57:50AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Aug 31, 2017 at 05:54:58PM +0100, Piotr Gregor wrote:
> > > This is a small and simple driver for handling of external
> > > interrupt signal asserted on
-Using-WARN_ON-rather-than-BUG/20170901-160600
config: s390-allmodconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin
-Using-WARN_ON-rather-than-BUG/20170901-160600
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget
https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
On Fri, Sep 01, 2017 at 08:57:50AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 31, 2017 at 05:54:58PM +0100, Piotr Gregor wrote:
> > This is a small and simple driver for handling of external
> > interrupt signal asserted on pins of Amplicon's PCIe215 board.
> > There is already a Comedi driver
On Fri, Sep 01, 2017 at 12:01:02PM +0530, Janani Sankara Babu wrote:
> This patch is created to solve the CamelCase issue. The members 'IEs' and
> 'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
> 'ie_length' to solve the issue. And all the places where these variables
> are
On 8/31/2017 7:19 PM, Greg Kroah-Hartman wrote:
> On Wed, Aug 30, 2017 at 01:42:02PM +0300, Horia Geantă wrote:
>> Previous commits:
>> 6e2387e8f19e ("staging: fsl-dpaa2/eth: Add Freescale DPAA2 Ethernet driver")
>> 39163c0ce0f4 ("staging: fsl-dpaa2/eth: Errors checking update")
>> have added bits
On Fri, Sep 01, 2017 at 08:14:16AM +, Horia Geantă wrote:
> On 8/31/2017 7:20 PM, Greg Kroah-Hartman wrote:
> > On Wed, Aug 30, 2017 at 01:41:58PM +0300, Horia Geantă wrote:
> >> This patch set adds support for functionalities needed by the upcoming
> >> dpseci (Data Path SEC Interface) object
On 8/31/2017 7:20 PM, Greg Kroah-Hartman wrote:
> On Wed, Aug 30, 2017 at 01:41:58PM +0300, Horia Geantă wrote:
>> This patch set adds support for functionalities needed by the upcoming
>> dpseci (Data Path SEC Interface) object device driver:
>> -Frame List Entries (FLEs)
>> -Congestion State
On Thu, Aug 31, 2017 at 02:00:54PM +0200, Martijn Coenen wrote:
> On Thu, Aug 31, 2017 at 1:32 PM, Peter Zijlstra wrote:
> > AFAIK people are actively working on fixing that.
>
> SCHED_DEADLINE was definitely looked at in the past. We certainly
> don't use it on our own
This patch is created to solve the CamelCase issue. The members 'IEs'
and 'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
'ie_length' to solve the issue. And the places where these variables
are referenced inside rtl8188eu driver are also changed.
Signed-off-by: Janani Sankara
This patch removes the unwanted braces and else statement inside the
function 'SecIsInPMKIDList'
Signed-off-by: Janani Sankara Babu
---
Changelog
V1 : Removed the else statement & Curly braces in If statement
V2 : Removed the comment and added preincrement of i inside the
On Thu, Aug 31, 2017 at 12:47:59PM -0400, Nick Fox wrote:
> jonathan...@gctsemi.com, linux-ker...@vger.kernel.org
> Bcc:
> Subject: Re: [PATCH v2] staging : gdm724x: Rename variable for consistency
> Reply-To:
> In-Reply-To: <20170831162747.ga31...@kroah.com>
What just happened there?
What
On Thu, Aug 31, 2017 at 05:54:58PM +0100, Piotr Gregor wrote:
> This is a small and simple driver for handling of external
> interrupt signal asserted on pins of Amplicon's PCIe215 board.
> There is already a Comedi driver subsystem in kernel which handles
> that (and more) board, but that
On Thu, Aug 31, 2017 at 10:26:06AM -0700, Sherry Yang wrote:
> Fix crash introduced by 74310e06be4d74dcf67cd108366710dee5c576d5
> (android: binder: Move buffer out of area shared with user space)
> when close is called after open without mmap in between.
>
> Signed-off-by: Sherry Yang
On Fri, Sep 01, 2017 at 12:01:02PM +0530, Janani Sankara Babu wrote:
> This patch is created to solve the CamelCase issue. The members 'IEs' and
> 'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
> 'ie_length' to solve the issue. And all the places where these variables
> are
This patch is created to solve the CamelCase issue. The members 'IEs' and
'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
'ie_length' to solve the issue. And all the places where these variables
are referenced inside rtl8188eu driver are also changed.
Signed-off-by: Janani
52 matches
Mail list logo