[linux-yocto] [PATCH] usb: mux: add module parameter to portmux-intel-drcfg

From: Wan Ahmad Zainie This patch add the following module parameter, usb0_init_state to override default USB port 0 role set by ABL/BIOS, and usb0_auto_role to set USB port 0 mux in automatic mode. By default, this driver will set the initial mode based

[linux-yocto] [PATCH] Add module parameter to portmux-intel-drcfg driver

From: Wan Ahmad Zainie Hi Bruce. This patch is to add two module parameters to portmux-intel-drcfg driver, to enable configuring USB port 0 of Apollo Lake during boot time. First one is usb0_init_state, to override the default mode of the port set by

[linux-yocto] [PATCH] usb: mux: add module parameter to portmux-intel-drcfg

From: Wan Ahmad Zainie This patch add the following module parameter, usb0_init_state to override default USB port 0 role set by ABL/BIOS, and usb0_auto_role to set USB port 0 mux in automatic mode. By default, this driver will set the initial mode based

[linux-yocto] [PATCH] Add module parameter to portmux-intel-drcfg driver

From: Wan Ahmad Zainie Hi Bruce. This is a resend. I mistakenly put a wrong from email address in my previous email. This patch is to add two module parameters to portmux-intel-drcfg driver, to enable configuring USB port 0 of Apollo Lake during boot

[linux-yocto] [PATCH 1/2] mfd: intel_vuport: use back property_set struct

From: Wan Ahmad Zainie Fix for this compilation error, drivers/mfd/intel-vuport.c:38:3: error: unknown field ‘properties’ specified in initializer .properties = reg_properties, due to missing commit f4d052660323 ("device property: don't bother the

[linux-yocto] [PATCH 2/2] usb: core: hub: generate uevent for over current condition

From: Wan Ahmad Zainie This modification generates a 'uevent' to userland and adds the 'OVERCURRENT=1' environment when overcurrent event happens and adds the 'OVERCURRENT=0' environment when returning to normal current condition, with PORT number. Any

[linux-yocto] [PATCH 7/9] mfd: intel_vuport: Add Intel virtual USB port MFD Driver

From: Lu Baolu Some Intel platforms have an USB port mux controlled by GPIOs. There's a single ACPI platform device that provides 1) USB ID extcon device; 2) USB vbus regulator device; and 3) USB port switch device. This MFD driver will split these 3 devices for their

[linux-yocto] [PATCH 8/9] usb: pci-quirks: add Intel USB drcfg mux device

From: Lu Baolu In some Intel platforms, a single usb port is shared between USB host and device controllers. The shared port is under control of a switch which is defined in the Intel vendor defined extended capability for xHCI. This patch adds the support to detect

[linux-yocto] [PATCH 6/9] usb: mux: add driver for Intel drcfg controlled port mux

From: Lu Baolu Several Intel PCHs and SOCs have an internal mux that is used to share one USB port between device controller and host controller. The mux is handled through the Dual Role Configuration Register. Signed-off-by: Heikki Krogerus

[linux-yocto] [PATCH 9/9] MAINTAINERS: add maintainer entry for Intel USB dual role mux drivers

From: Lu Baolu Add a maintainer entry for Intel USB dual role mux drivers and add myself as a maintainer. Signed-off-by: Lu Baolu Signed-off-by: Wan Ahmad Zainie --- MAINTAINERS | 10 ++ 1

[linux-yocto] [PATCH 5/9] usb: mux: add driver for Intel gpio controlled port mux

From: Lu Baolu In some Intel platforms, a single usb port is shared between USB host and device controller. The shared port is under control of GPIO pins. This patch adds the support for USB GPIO controlled port mux. [baolu: removed .owner per

[linux-yocto] [PATCH 4/9] usb: mux: add generic code for dual role port mux

From: Lu Baolu Several Intel platforms implement USB dual role by having completely separate xHCI and dwc3 IPs in PCH or SOC silicons. These two IPs share a single USB port. There is another external port mux which controls where the data lines should go. While the USB

[linux-yocto] [PATCH 3/9] regulator: fixed: add support for ACPI interface

From: Lu Baolu Add support to retrieve fixed voltage configure information through ACPI interface. This is needed for Intel Bay Trail devices, where a GPIO is used to control the USB vbus. Signed-off-by: Lu Baolu Signed-off-by: Wan Ahmad

[linux-yocto] [PATCH 0/9] usb: add support for Intel dual role port mux

From: Wan Ahmad Zainie Hi Bruce. Complete information for this patch series is available at URL below, https://lwn.net/Articles/689134/ It is not accepted to the mainline Linux kernel. However, this is the method that we have at this moment to control

[linux-yocto] [PATCH 2/9] extcon: usb-gpio: add support for ACPI gpio interface

From: Lu Baolu GPIO resource could be retrieved through APCI as well. Signed-off-by: Lu Baolu Reviewed-by: Felipe Balbi Acked-by: Chanwoo Choi Signed-off-by: Wan Ahmad Zainie

[linux-yocto] [PATCH 7/8] device property: convert to use match_string() helper

From: Andy Shevchenko The new helper returns index of the mathing string in an array. We would use it here. Signed-off-by: Andy Shevchenko Reviewed-by: Mika Westerberg Acked-by: Rafael J.

[linux-yocto] [PATCH 8/8] device property: Avoid potential dereferences of invalid pointers

From: Heikki Krogerus Since fwnode may hold ERR_PTR(-ENODEV) or it may be NULL, the fwnode type checks is_of_node(), is_acpi_node() and is is_pset_node() need to consider it. Using IS_ERR_OR_NULL() to check it. Fixes: 0d67e0fa1664 (device property: fix for a

[linux-yocto] [PATCH 6/8] lib/string: introduce match_string() helper

From: Andy Shevchenko Occasionally we have to search for an occurrence of a string in an array of strings. Make a simple helper for that purpose. Signed-off-by: Andy Shevchenko Cc: "David S. Miller"

[linux-yocto] [PATCH 5/8] device property: fix for a case of use-after-free

From: Heikki Krogerus In device_remove_property_set(), the secondary fwnode needs to be cleared before the pset is freed. This fixes a use-after-free when a property set is providing the primary fwnode. As a result of the fix, the primary fwnode may end up

[linux-yocto] [PATCH 2/8] xhci: rework xhci extended capability list parsing functions

From: Mathias Nyman Replace the existing two extended capability parsing helper functions with one called xhci_find_next_ext_cap(). The extended capabilities are read both in pci-quirks before xhci driver is loaded, and inside the xhci driver when adding ports.

[linux-yocto] [PATCH 1/8] xhci: parse xhci protocol speed ID list for usb 3.1 usage

From: Mathias Nyman xhci 1.1 controllers that support USB 3.1 must provide a protocol speed ID (PSI) list to inform the driver of the supported speeds. The PSI list can be read from the xhci supported protocol extended capabilities. The PSI values will be used to

[linux-yocto] [PATCH 0/8] Backport some USB patches to 4.1

From: Wan Ahmad Zainie Hi Bruce. These patches are USB dependency patches for the patch series usb: add support for Intel dual role port mux. More info at URL below. https://lwn.net/Articles/689134/ All of them are from mainline Linux kernel, thus they

[linux-yocto] [PATCH 3/8] xhci: harden xhci_find_next_ext_cap against device removal

From: Joe Lawrence xhci_find_next_ext_cap doesn't check for PCI hotplug removal and may use the PCI master abort bit pattern (~0) to calculate a new PCI address offset to read/write. The has lead to reproducable crashes when testing surprise removal during device

[linux-yocto] [PATCH 4/8] device property: fwnode->secondary may contain ERR_PTR(-ENODEV)

From: Heikki Krogerus This fixes BUG triggered when fwnode->secondary is not NULL, but has ERR_PTR(-ENODEV) instead. BUG: unable to handle kernel paging request at ffed IP: [] __fwnode_property_read_string+0x26/0x160 PGD 200e067 PUD 2010067 PMD 0

[linux-yocto] [PATCH 13/14] extcon: Remove optional print_name() function pointer of extcon_dev

From: Chanwoo Choi This patch removes the optional print_name() function pointer included in 'struct extcon_dev' because the extcon must maintain the consistent name of extcon device on sysfs instead of inconsistent name. After merged patch[1], extcon can maintain the

[linux-yocto] [PATCH 14/14] extcon: Redefine the unique id of supported external connectors without 'enum extcon' type

From: Chanwoo Choi This patch just redefine the unique id of supported external connectors without 'enum extcon' type. Because unique id would be used on devictree file(*.dts) to indicate the specific external connectors like key number of input framework. So, I have the

[linux-yocto] [PATCH 11/14] extcon: Use capital letter for the name of external connectors

From: Chanwoo Choi This patch uses the capital letter for the name of external connectors to improve the readability instead of small letter. Cc: MyungJoo Ham Signed-off-by: Chanwoo Choi (cherry picked from commit

[linux-yocto] [PATCH 08/14] extcon: adc-jack: Remove the unneeded num_cables field

From: Chanwoo Choi This patch removes the 'num_cables' filed from 'struct adc_jack_pdata' because 'struct extcon_dev' contains the 'max_supported' field which means the number of supported cable of extcon device. Signed-off-by: Chanwoo Choi (cherry

[linux-yocto] [PATCH 06/14] extcon: Unify the dock device names on max8997/77693

From: Chanwoo Choi This patch change the name of various dock devices as 'DOCK' because the name of various dock devices have not the standard naming rules. The name of dock devices include the differenct word but it is ambiguous and never important information on

[linux-yocto] [PATCH 09/14] extcon: Remove the optional name of extcon device

From: Chanwoo Choi This patch removes the optional name of extcon device. Instead, extcon_dev_register() set the device name as 'extcon[number]' naming pattern. - /sys/class/extcon/[hardcoded device name] -> /sys/class/extcon/extcon[number] Signed-off-by: Chanwoo Choi

[linux-yocto] [PATCH 10/14] extcon: Use the unique id for external connector instead of string

From: Chanwoo Choi This patch uses the unique id to identify the type of external connector instead of string name. The string name have the many potential issues. So, this patch defines the 'extcon' enumeration which includes all supported external connector on EXTCON

[linux-yocto] [PATCH 07/14] extcon: Alter MHL-TA cable name to TA cable name

From: Chanwoo Choi This patch alters the MHL-TA cable name to TA cable name because MHL-TA is not standard name. The MHL-TA is MHL cable with charger cable (TA or USB). So, this patch use the TA cable instead of MHL-TA to inform the charger cable state. - MHL-TA -> TA

[linux-yocto] [PATCH 00/14] Backport some extcon patches to 4.1

From: Wan Ahmad Zainie Hi Bruce. These patches are extcon dependency patches for the patch series usb: add support for Intel dual role port mux. More info at URL below. https://lwn.net/Articles/689134/ All of them are from mainline Linux kernel, thus

[linux-yocto] [PATCH 01/14] extcon: Add manufactor name of each extcon device

From: Chanwoo Choi This patch adds the manufactor name of each extcon device and removes un-necessary comment in Kconfig. Signed-off-by: Chanwoo Choi (cherry picked from commit ed2c0604ace93a2c9b8fc055ab61fff68704cd1e) Signed-off-by: Wan Ahmad

[linux-yocto] [PATCH 05/14] extcon: Unify the jig cable names on rt8973 and max14577/77693/77843

From: Chanwoo Choi This patch change the name of various jig cables as 'JIG' because the name of various jig cables are strange and ambiguous on user-space aspect. They include the different information of either USB and UART state. It is never important for user-space

[linux-yocto] [PATCH 03/14] extcon: Add extcon_get_edev_name() API to get the extcon device name

From: Chanwoo Choi This patch adds the extcon_get_edev_name() API to get the name of extcon device because all information inclued in the structure extcon_dev should be accessed by extcon core API instead of directly accessing the data. Signed-off-by: Chanwoo Choi

[linux-yocto] [PATCH 04/14] extcon: Fix the checkpatch warning and minor coding style issue

From: Chanwoo Choi This patch clean up the extcon core driver by fixing the checkpatch warning and minor coding style issue. Signed-off-by: Chanwoo Choi (cherry picked from commit b9ec23c08a0274d31ee626f14b359563ea0cae46) Signed-off-by: Wan Ahmad

[linux-yocto] [PATCH 13/25] usb: chipidea: set usb otg capabilities

From: Li Jun Init and update otg capabilities by DT, set gadget's otg capabilities accordingly. Acked-by: Peter Chen Reviewed-by: Roger Quadros Signed-off-by: Li Jun Signed-off-by: Felipe Balbi

[linux-yocto] [PATCH 25/25] usb: dwc3: pci: add support for Intel Broxton SOC

From: Heikki Krogerus PCI IDs for Broxton based platforms. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe Balbi (cherry picked from commit b4c580a43d520b7812c0fd064fbab929ce2f1da0) Signed-off-by: Wan Ahmad

[linux-yocto] [PATCH 10/25] usb: dwc3: add ULPI interface support

From: Heikki Krogerus Registers DWC3's ULPI interface with the ULPI bus when it's available. Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe Balbi (cherry

[linux-yocto] [PATCH 24/25] usb: dwc3: pci: Set enblslpm quirk for Synopsys platforms

From: John Youn Certain Synopsys prototyping PHY boards are not able to meet timings constraints for LPM. This allows the PHY to meet those timings by leaving the PHY clock running during suspend. Cc: # v3.18+ Signed-off-by: John Youn

[linux-yocto] [PATCH 11/25] usb: dwc3: core: avoid NULL pointer dereference

From: Felipe Balbi commit 3e10a2ce98d1 ("usb: dwc3: add hsphy_interface property") introduced a possible NULL pointer dereference because dwc->hsphy_interface can be NULL. In order to fix it, all we have to do is guard strncmp() against a NULL argument. Fixes: 3e10a2ce98d1 ("usb:

[linux-yocto] [PATCH 07/25] usb: dwc3: setup phys earlier

From: Heikki Krogerus This allows dwc3_phy_setup() to be more useful later. There is nothing preventing the PHY configuration registers from being programmed early. They do not loose their context in soft reset. There are however other PHY related operations

[linux-yocto] [PATCH 19/25] usb: common: of_usb_get_dr_mode to usb_get_dr_mode

From: Heikki Krogerus By using the unified device property interface, the function can be made available for all platforms and not just the ones using DT. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe Balbi

[linux-yocto] [PATCH 09/25] usb: dwc3: pci: add quirk for Baytrails

From: Heikki Krogerus On some BYT platforms the USB2 PHY needs to be put into operational mode by the controller driver with GPIOs controlling the PHYs reset and cs signals. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe

[linux-yocto] [PATCH 20/25] usb: dwc3: core: convert to unified device property interface

From: Heikki Krogerus No functional affect on existing platforms, but the driver is now ready to extract the properties also from ACPI tables as well as from DT. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe Balbi

[linux-yocto] [PATCH 21/25] usb: dwc3: pci: passing forward the ACPI companion

From: Heikki Krogerus Sharing the ACPI companion with dwc3 core so it has access to the properties defined for DWC3 in ACPI tables. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe Balbi (cherry picked from

[linux-yocto] [PATCH 14/25] usb: renesas_usbhs: Allow an OTG PHY driver to provide VBUS

From: Phil Edworthy These changes allow a PHY driver to trigger a VBUS interrupt and to provide the value of VBUS. Reviewed-by: Laurent Pinchart Signed-off-by: Phil Edworthy Signed-off-by: Felipe Balbi

[linux-yocto] [PATCH 17/25] usb: common: of_usb_get_maximum_speed to usb_get_maximum_speed

From: Heikki Krogerus By using the unified device property interface, the function can be made available for all platforms and not just the ones using DT. Signed-off-by: Heikki Krogerus Signed-off-by: Felipe Balbi

[linux-yocto] [PATCH 06/25] usb: dwc3: soft reset to it's own function

From: Heikki Krogerus So it can be called from other places later. Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe Balbi (cherry picked from commit

[linux-yocto] [PATCH 16/25] usb: dwc3: Add frame length adjustment quirk

From: Nikhil Badola Add adjust_frame_length_quirk for writing to fladj register which adjusts (micro)frame length to value provided by "snps,quirk-frame-length-adjustment" property thus avoiding USB 2.0 devices to time-out over a longer run Signed-off-by: Nikhil

[linux-yocto] [PATCH 18/25] usb: dwc3: st: prepare the driver for generic usb_get_dr_mode function

From: Heikki Krogerus of_usb_get_dr_mode will be converted into more generic usb_get_dr_mode function that will take struct device instead of struct device_node as its parameter. To make the conversion possible later, waiting for the platform device for dwc3 to

[linux-yocto] [PATCH 15/25] usb: musb: dsps: control musb speed based on dts setting

From: Bin Liu Set musb config->maximum_speed based on the dts setting to control musb speed. By default musb works in high-speed mode. Adding maximum-speed = "full-speed"; to dts usb node will force musb to full-speed mode. Signed-off-by: Bin Liu

[linux-yocto] [PATCH 05/25] usb: dwc3: cache hwparams earlier

From: Heikki Krogerus So they are available when ULPI interface support is added. Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe Balbi (cherry picked

[linux-yocto] [PATCH 04/25] usb: dwc3: store driver data earlier

From: Heikki Krogerus We need to store it before phys are handled, so we can later use it in ULPI interface support code. Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe

[linux-yocto] [PATCH 03/25] usb: dwc3: ULPI or UTMI+ select

From: Heikki Krogerus Make selection between ULPI and UTMI+ interfaces possible by providing definition for the bit in Global USB2 PHY Configuration Register that controls it. Signed-off-by: Heikki Krogerus Acked-by: David Cohen

[linux-yocto] [PATCH 02/25] usb: dwc3: USB2 PHY register access bits

From: Heikki Krogerus Definitions for Global USB2 PHY Vendor Control Register bits. We will need them to access ULPI PHY registers later. Signed-off-by: Heikki Krogerus Acked-by: David Cohen

[linux-yocto] [PATCH 01/25] usb: add bus type for USB ULPI

From: Heikki Krogerus UTMI+ Low Pin Interface (ULPI) is a commonly used PHY interface for USB 2.0. The ULPI specification describes a standard set of registers which the vendors can extend for their specific needs. ULPI PHYs provide often functions such as

[linux-yocto] [PATCH 00/25] Backport some USB patches to 4.1

From: Wan Ahmad Zainie Hi Bruce. These patches are the USB backports for Apollo Lake/Broxton, upstreamed to the mainline Linux kernel by Heikki Krogerus. The patch usb: dwc3: core: avoid NULL pointer dereference is to guard against a possible NULL

[linux-yocto] [PATCH 1/6] Revert "dmaengine: dw: move clock operations to platform.c"

From: "Ng, Wei Tee" This reverts commit a2adfa19c6f9adb33e1c11cacf02f0e06e166434. Signed-off-by: Ng, Wei Tee --- drivers/dma/dw/core.c | 11 +++ drivers/dma/dw/internal.h | 2 -- drivers/dma/dw/platform.c | 25 +++--

[linux-yocto] [PATCH 0/6] [linux-yocto-3.10] valleyisland-io-4.0: Updated for Bay Trail IO

From: Wan Ahmad Zainie Hi. This patch is to update the feature branch (valleyisland-io-4.0) with the following changes: 1. Rearrange the dmaengine commits in the correct order. 2. Update of i2c-designware for mode switching. It was built with Valley

[linux-yocto] [PATCH 2/6] dmaengine: dw: apply both HS interfaces and remove slave_id usage

From: Andy Shevchenko Instead of one request line member let's use both source and destination ones. Usually we have no such hardware except Atmel MMC controller found on AVR32 platform (see arch/avr32/mach-at32ap/at32ap700x.c and drivers/mmc/host/atmel-mci.c).

[linux-yocto] [PATCH 1/2] serial: 8250: don't use slave_id of dma_slave_config

From: Andy Shevchenko That field has been deprecated in favour of getting the necessary information from ACPI or DT. However, we still need to deal systems that are PCI only (no ACPI to back up) like Intel Bay Trail. In order to support such systems, we

[linux-yocto] [PATCH 3/6] dmaengine: dw: move clock operations to platform.c

From: Andy Shevchenko On BayTrail platform DMA is not functional in the PCI mode, whereby it always failed and exit at the point when it tries to get a clock. It causes the PCI mode probe to exit with the error message: dw_dmac_pci: probe of

[linux-yocto] [PATCH 5/6] i2c: allow Designware I2C to be probed before SMBus for Baytrail

From: Maurice Petallo When SMBus is enabled in Baytrail, it is being probed first before all the Designware I2C devices. This means SMBus will take the first available bus id which is 0 and then the I2C devices will take the next succeeding bus ids. This should be

[linux-yocto] [PATCH 2/2] spi/pxa2xx: Don't use slave_id of dma_slave_config

From: Mika Westerberg That field has been deprecated in favour of getting the necessary information from ACPI/DT. However, we still need to deal systems that are PCI only (no ACPI to back up). In order to support such systems, we allow the DMA filter function

[linux-yocto] [PATCH 6/6] i2c: designware: enable fast and standard speed mode switching

From: cchew14 This patch applies the change to both platform and pci driver For built-in driver, insert i2c-designware-pci.force_std_mode=1 for LPSS PCI Mode or i2c-designware-platform.force_std_mode=1 for LPSS ACPI Mode in kernel boot configuration. v3: - Nothing was