[linux-yocto] [PATCH 16/17] i2c: designware: Do not require clock when SSCN and FFCN are provided

From: Suravee Suthikulpanit The current driver uses input clock source frequency to calculate values for [SS|FS]_[HC|LC] registers. However, when booting ACPI, we do not currently have a good way to provide the frequency information. Instead, we can leverage the

[linux-yocto] [PATCH 17/17] i2c: designware: Convert to use unified device property API

From: Mika Westerberg With ACPI _DSD (introduced in ACPI v5.1) it is now possible to pass device configuration information from ACPI in addition to DT. In order to support this, convert the driver to use the unified device property accessors instead of DT

[linux-yocto] [PATCH 12/17] i2c: designware: Make dw_readl() and dw_writel() static

From: Jarkko Nikula dw_readl() and dw_writel() are not used outside of i2c-designware-core and they are not exported so make them static and remove their forward declaration. Signed-off-by: Jarkko Nikula Signed-off-by: Wolfram Sang

[linux-yocto] [PATCH 11/17] i2c: designware: Remove unused functions

From: Jarkko Nikula i2c_dw_is_enabled() became unused by the commit be58eda775c8 ("i2c: designware-pci: Cleanup driver power management") and i2c_dw_enable() by the commit 3a48d1c08fe0 ("i2c: prevent spurious interrupt on Designware controllers"). Signed-off-by:

[linux-yocto] [PATCH 13/17] i2c: designware: Rename platform driver probe and PM functions

From: Jarkko Nikula Make it easier to distinguish between i2c-designware-platdrv and i2c-designware-core functions and to be consistent with i2c-designware-pcidrv. Signed-off-by: Jarkko Nikula Signed-off-by: Wolfram Sang

[linux-yocto] [PATCH 14/17] i2c: designware: Move common probe code into i2c_dw_probe()

From: Jarkko Nikula There is some code duplication in i2c-designware-platdrv and i2c-designware-pcidrv probe functions. What is even worse that duplication requires i2c_dw_xfer(), i2c_dw_func() and i2c_dw_isr() i2c-designware-core functions to be exported.

[linux-yocto] [PATCH 10/17] i2c: designware: Disable interrupts before requesting PCI device interrupt

From: Jarkko Nikula Device must not generate interrupts before registering the interrupt handler so move i2c_dw_disable_int() before requesting it. There are no known issues with this. The code has been here since commit fe20ff5c7e9c ("i2c-designware: Add support

[linux-yocto] [PATCH 08/17] i2c: designware: Make debug print in i2c_dw_isr() shorter

From: Jarkko Nikula Printing adapter name is irrelevant from this debug print and makes output needlessly long. Having already device and functions names printed here is enough for debugging. While at it remove extra space from "enabled= 0x" and use "%#x" for

[linux-yocto] [PATCH 04/17] i2c: designware: Add support for AMD Seattle I2C

From: Suravee Suthikulpanit Add device HID AMDI0510 to match the I2C controlers on AMD Seattle platform Signed-off-by: Suravee Suthikulpanit Signed-off-by: Wolfram Sang (cherry picked from commit

[linux-yocto] [PATCH 07/17] i2c: designware-pci: use IRQF_COND_SUSPEND flag

From: Andy Shevchenko The mentioned flag fixes a warning on Intel Edison board since one of the I2C controller shares IRQ line with watchdog timer. Signed-off-by: Andy Shevchenko Acked-by: Mika Westerberg

[linux-yocto] [PATCH 01/17] i2c: designware: use to_pci_dev()

From: Geliang Tang Use to_pci_dev() instead of open-coding it. Signed-off-by: Geliang Tang Reviewed-by: Andy Shevchenko Signed-off-by: Wolfram Sang (cherry picked from commit

[linux-yocto] [PATCH 06/17] i2c: designware: Avoid unnecessary resuming during system suspend

From: Jisheng Zhang Commit 1fc2fe204cb9 ("i2c: designware: Add runtime PM hooks") adds runtime pm support using the same ops for system pm and runtime pm. When suspend to ram, the i2c host may have been runtime suspended, thus i2c_dw_disable() hangs. Previously, I fixed

[linux-yocto] [PATCH 05/17] i2c: dw: Add APM X-Gene ACPI I2C device support

From: Loc Ho Enable APM X-Gene ACPI I2C device support by adding the corresponding ACPI ID. The platform ACPI APD corresponding change is required to provide the proper clock frequency input. Signed-off-by: Loc Ho Acked-by: Mika Westerberg

[linux-yocto] [PATCH 02/17] i2c: designware: reverts "i2c: designware: Add support for AMD I2C controller"

From: Ken Xue The patch reverts commit a445900c9060 (i2c: designware: Add support for AMD I2C controller). It never worked anyhow because it did not register a proper clkdev. Since kernel 4.1 starts to support APD, there is no need to get freq from id->driver_data for AMD0010.

[linux-yocto] [PATCH 00/17] i2c: designware: Backport i2c patches to 4.1

From: "Voon, Weifeng" This i2c patches are needed to be backported to enable Apollo Lake/Broxton This patches are from mainline and targeted for linux-yocto-4.1 on standard/base branch Andy Shevchenko (1): i2c: designware-pci: use IRQF_COND_SUSPEND flag Baruch Siach

Re: [yocto] [meta-raspberrypi][PATCH 4/6] linux-firmware: Add brcmfmac43430 firmware

Hi Theodor, On 10 March 2016 at 01:15, Theodor Gherzan wrote: > From: Theodor Gherzan > > Signed-off-by: Theodor Gherzan > --- > .../linux-firmware/LICENSE.broadcom_brcm80211 | 205 > + >

Re: [yocto] [oe] [OE-core] OEDAM, April 8 in San Diego after ELC

Since I happen to live in San Diego, I have been asking around for a potential meeting room (unfortunately, I don't have an office with a meeting room myself). I am currently working with the University of San Diego and the Catamaran/Bahia Hotel. Can't promise anything yet. :rjs On Thursday,

Re: [yocto] [OE-core] [oe] OEDAM, April 8 in San Diego after ELC

We are up to fifteen now and as noted will have some off site attendees and late sign ups. Philip On 03/23/2016 02:11 PM, Fred Ollinger wrote: > I'm coming and I'm probably brining another person. > > I still have to make the wiki account which failed for some reason before. > > Frederick >

[yocto] Hung build when doing Kernel Training Lab

I've been working through the Kernel Training labs from https://www.yoctoproject.org/sites/default/files/kernel-lab-1.6.pdf. Everything is working as expected up - using Poky 1.6.03 - until I get to Lab 4. In lab 4, the kernel source is coming from a local clone of the git repository:

Re: [linux-yocto] Backport Device Property from Linux-4.4 to linux-yocto-4.1

On Wed, Mar 23, 2016 at 11:31 PM, Yong, Jonathan wrote: > On 03/24/2016 06:09, Bruce Ashfield wrote: > >> >> No worries. I fetched the branch. I see 18 commits in your summary, but >> I'm >> still seeing duplicates >> on what I fetched. >> >> i.e. the branch I just