Re: [linux-yocto] [PATCH 00/18] Backport serial patches from mainline kernel into linux-yocto-4.1

On 2016-06-10 03:52 AM, Tan Jui Nee wrote: Hi Bruce, These patches are the serial backports for Intel Apollo Lake/Broxton, that are available in mainline Linux kernel. All the patches are to enable serial driver support for Intel Apollo Lake/ Broxton. The patches are targeted to merge into

Re: [linux-yocto] [PATCH] Backport iDMA64 patches from mainline kernel into linux-yocto-4.1

On 2016-06-10 03:42 AM, Tan Jui Nee wrote: Hi Bruce, The patch is to rename symbol CONFIG_IDMA64 to CONFIG_INTEL_IDMA64, as to conform to rest of the intel dmaengine drivers. The patch is targeted to merge into linux-yocto-4.1 on standard/base branch. Looks fine to me. I've staged the

Re: [linux-yocto] [PATCH 0/8] mmc: sdhci: Enable MMC_CAP_AGGRESSIVE_PM for Broxton controllers

On 2016-06-10 02:21 AM, Lim Key Seong wrote: Hi Bruce, These patches are backport for enabling MMC aggressive PM for Broxton controllers. Two patches on enabling MMC_CAP_AGGRESIVE_PM had upstream to mainline Linux Kernel by Adrian Hunter. The rest of 6 patches are dependency patches to apply

Re: [linux-yocto] [PATCH] mtd: spi-nor: add support for w25q128fw to linux-yocto-4.1

On 2016-06-09 05:50 AM, Lim Key Seong wrote: Hi Bruce, This patch is backport for enabling winbond SPI Flash - w25q128fw that upstreamed to the mainline Linux Kernel by Brian Norris. This patch is targeted for linux-yocto-4.1, standard/base branch. Looks good. I see this arrived in mainline

Re: [linux-yocto] [PATCH 0/1] kernel-cache: common-pc-64.scc: add efi-ext

On 2016-06-07 04:54 PM, Jianxun Zhang wrote: This patch is ported from 3.14 meta to master branch in kernel cache. But it should be to all 4.x branches since it is a common feature for x86 and 32 bit scc already has it. Note: We skipped test before this submission, assuming test result done on

[linux-yocto] [PATCH 18/18] serial: 8250_dw: Do not use readl/writel before checking port iotype

From: Noam Camus Direct call to readl()/writel() is checked against iotype and in case of UPIO_MEM32BE we use ioread32be()/iowrite32be() instead of them. Signed-off-by: Noam Camus Signed-off-by: Greg Kroah-Hartman (cherry picked

[linux-yocto] [PATCH 13/18] serial: 8250_dw: cleanup dw8250_idma_filter

From: Heikki Krogerus Remove the extra return. Signed-off-by: Heikki Krogerus Reviewed-by: Andy Shevchenko Signed-off-by: Greg Kroah-Hartman (cherry picked from

[linux-yocto] [PATCH 12/18] serial: 8250_dw: rename and comment the fallback dma filter

From: Heikki Krogerus Adding comment where the purpose of the function is explained. The dma parameters are not used, so removing them, and also moving the assignment of the function to the same place where the other dw8250_data structures members are being set

[linux-yocto] [PATCH 16/18] serial: 8250_dw: Avoid serial_outx code duplicate with new dw8250_check_lcr()

From: Noam Camus With the help of Heikki we take common code that makes sure LCR write wasn't ignored and put it in new function called dw8250_check_lcr(). This function serves 3 serial_out routines: dw8250_serial_out(), dw8250_serial_out32(), and dw8250_serial_outq(). This

[linux-yocto] [PATCH 15/18] serial: 8250_dw: don't set UPF_BOOT_AUTOCONF flag

From: Heikki Krogerus serial8250_register_8250_port adds it to all ports it registers. No need to set it separately. Signed-off-by: Heikki Krogerus Reviewed-by: Andy Shevchenko Signed-off-by:

[linux-yocto] [PATCH 14/18] serial: 8250_dw: cleanup dw8250_setup_port

From: Heikki Krogerus Using the same style of declaring variables as used in the other functions of the driver. Passing uart_port to the function instead of uart_8250_port, as it is the one mostly needed. Signed-off-by: Heikki Krogerus

[linux-yocto] [PATCH 11/18] serial: 8250_dw: proper support for UARTs without busy functionality

From: Heikki Krogerus If the DW_apb_uart is configured with UART_16550_COMPATIBLE configuration parameter set, then the Busy Functionality is not available. These UARTs will never generate the Busy detect indication interrupt, and therefore don't need handling

[linux-yocto] [PATCH 17/18] serial: 8250_dw: Add support for big-endian MMIO accesses

From: Noam Camus Add support for UPIO_MEM32BE in addition to UPIO_MEM32. For big endian we use 2 new accessors similar to little endian, called dw8250_serial_out32be() and dw8250_serial_in32be(). Signed-off-by: Noam Camus Signed-off-by: Greg Kroah-Hartman

[linux-yocto] [PATCH 10/18] serial: 8250_dw: add dw8250_quirks function

From: Heikki Krogerus Merging the DT and ACPI specific probe functions into dw8250_quirks. Those functions did not have that much code any more and some of the quirks need to be shared. This will also allow platforms without DT or ACPI to use the driver.

[linux-yocto] [PATCH 09/18] serial: 8250_dw: only setup the port from one place

From: Heikki Krogerus This adds a flag "skip_autocfg" that the platforms that do not have the ADDITIONAL_FEATURES implemented can use to skip the port setup. It's then enough to call dw8250_setup_port just from dw8250_probe based on that flag. Signed-off-by:

[linux-yocto] [PATCH 07/18] serial: 8250_dw: adapt to unified device property interface

From: Heikki Krogerus This makes the properties available for all types of platforms instead of just the ones using DT. Signed-off-by: Heikki Krogerus Reviewed-by: Andy Shevchenko

[linux-yocto] [PATCH 08/18] serial: 8250_dw: hook the DMA in one place

From: Heikki Krogerus Instead of assigning the dma member in dw8250_probe_of and dw8250_probe_acpi separately, assigning it in dw8250_probe. Signed-off-by: Heikki Krogerus Reviewed-by: Andy Shevchenko

[linux-yocto] [PATCH 06/18] serial: 8250_dw: add separate pointer for the uart_port to dw8250_probe

From: Heikki Krogerus For convenience, adding separate pointer for the "port" member of struct uart_8250_port that is being filled in the probe function. Signed-off-by: Heikki Krogerus Reviewed-by: Andy Shevchenko

[linux-yocto] [PATCH 05/18] serial: 8250_dw: allow lower reference frequencies

From: Andy Shevchenko We have couple of standard but rare used baudrates which are not supported by 1,8432MHz reference frequency. Besides that user can potentially ask for any baudrate (via BOTHER flag) and we currently don't fully support that. Since

[linux-yocto] [PATCH 00/18] Backport serial patches from mainline kernel into linux-yocto-4.1

Hi Bruce, These patches are the serial backports for Intel Apollo Lake/Broxton, that are available in mainline Linux kernel. All the patches are to enable serial driver support for Intel Apollo Lake/ Broxton. The patches are targeted to merge into linux-yocto-4.1 on standard/base branch.

[linux-yocto] [PATCH 01/18] serial: 8250_dma: no need to sync RX buffer

From: Andy Shevchenko RX buffer is allocated from DMA coherent memory. Thus there is no need to call DMA sync API for it. Signed-off-by: Andy Shevchenko Signed-off-by: Greg Kroah-Hartman (cherry

[linux-yocto] [PATCH 04/18] serial:8250_dw: do not alter CTS and DCTS since AFE is enabled

From: Qipeng Zha Since the serial core is informed that this device is doing automatic flow control, it is not necessary to alter CTS and DCTS of the MSR as the core no longer attempts stop the port in uart_handle_cts_change(). Signed-off-by: Huiquan Zhong

[linux-yocto] [PATCH 02/18] serial: 8250_dw: support ACPI platforms with integrated DMA engine

From: Heikki Krogerus On many new Intel SoCs the UART has an integrated DMA engine (iDMA). In order to use it a special filter function is needed. Signed-off-by: Heikki Krogerus Signed-off-by: Greg Kroah-Hartman

[linux-yocto] [PATCH 03/18] serial: 8250: Auto CTS control by HW if AFE enabled

From: Qipeng Zha According to DesignWare 8250 spec, if auto flow control mode is enabled, a change in CTS does not cause an interrupt, so sw-assisted CTS flow control mode will not work properly. There reported an GPS firmware download failure issue, and we verified the

[linux-yocto] [PATCH] dmaengine: idma: rename to INTEL_IDMA64

From: Vinod Koul the symbol CONFIG_IDMA64 should rather be CONFIG_INTEL_IDMA64 to conform to rest of the intel dmaengine drivers. This was found after sorting the entries and trying to place this odd one Suggested-by: Linus Torvalds

[linux-yocto] [PATCH] Backport iDMA64 patches from mainline kernel into linux-yocto-4.1

Hi Bruce, The patch is to rename symbol CONFIG_IDMA64 to CONFIG_INTEL_IDMA64, as to conform to rest of the intel dmaengine drivers. The patch is targeted to merge into linux-yocto-4.1 on standard/base branch. Please review and provide feedback if any. Thanks and best regards, Juinee Vinod

[linux-yocto] [PATCH 8/8] mmc: sdhci-acpi: Set MMC_CAP_AGGRESSIVE_PM for Broxton controllers

From: Adrian Hunter Set MMC_CAP_AGGRESSIVE_PM for Broxton host controllers. Signed-off-by: Adrian Hunter Signed-off-by: Ulf Hansson (cherry picked from commit 706e86e9de7cfd5220784f6329d92f65de883d71) Signed-off-by: Lim

[linux-yocto] [PATCH 6/8] mmc: sdhci-pci: Add support and PCI IDs for more Broxton host controllers

From: Adrian Hunter Add support and PCI IDs for more Broxton host controllers Other BXT IDs were added in v4.4 so cc'ing stable. This patch is dependent on commit 163cbe31e516 ("mmc: sdhci-pci: Fix card detect race for Intel BXT/APL") but that is already in stable since

[linux-yocto] [PATCH 3/8] mmc: sdhci: Allow override of get_cd() called from sdhci_request()

From: Adrian Hunter Drivers may need to provide their own get_cd() mmc host op, but currently the internals of the current op (sdhci_get_cd()) are provided by sdhci_do_get_cd() which is also called from sdhci_request(). To allow override of the get_cd functionality,

[linux-yocto] [PATCH 4/8] mmc: sdhci-pci: Fix card detect race for Intel BXT/APL

From: Adrian Hunter Intel BXT/APL use a card detect GPIO however the host controller will not enable bus power unless it's card detect also reflects the presence of a card. Unfortunately those 2 things race which can result in commands not starting, after which the

[linux-yocto] [PATCH 2/8] mmc: sdhci: Allow override of mmc host operations

From: Adrian Hunter In the past, fixes for specific hardware devices were implemented in sdhci using quirks. That approach is no longer accepted because the growing number of quirks was starting to make the code difficult to understand and maintain. One alternative to

[linux-yocto] [PATCH 7/8] mmc: sdhci-pci: Set MMC_CAP_AGGRESSIVE_PM for Broxton controllers

From: Adrian Hunter Set MMC_CAP_AGGRESSIVE_PM for Broxton host controllers. Signed-off-by: Adrian Hunter Signed-off-by: Ulf Hansson (cherry picked from commit e8ef51763106dc40037c9ae207acf505bb4b71b1) Signed-off-by: Lim

[linux-yocto] [PATCH 5/8] mmc: sdhci-acpi: Fix card detect race for Intel BXT/APL

From: Adrian Hunter Intel BXT/APL use a card detect GPIO however the host controller will not enable bus power unless it's card detect also reflects the presence of a card. Unfortunately those 2 things race which can result in commands not starting, after which the

[linux-yocto] [PATCH 0/8] mmc: sdhci: Enable MMC_CAP_AGGRESSIVE_PM for Broxton controllers

Hi Bruce, These patches are backport for enabling MMC aggressive PM for Broxton controllers. Two patches on enabling MMC_CAP_AGGRESIVE_PM had upstream to mainline Linux Kernel by Adrian Hunter. The rest of 6 patches are dependency patches to apply two aggressive PM patches cleanly. There are

[linux-yocto] [PATCH 1/8] mmc: sdhci: make max-frequency property in device tree work

From: Dong Aisheng Device tree provides option to specify the max freqency with property "max-frequency" in dts and common parse function mmc_of_parse() will parse it and use this value to set host->f_max to tell the MMC core the maxinum frequency the host works.