Re: [PATCH V6 1/6] i2c: Add i2c support to Freescale Layerscape platforms

On Fri, Oct 23, 2015 at 04:01:17PM +0800, Zhiqiang Hou wrote: > From: Shaohui Xie > > Modify the I2C_IMX config to support to Layerscape platforms. > > Signed-off-by: Shaohui Xie > Signed-off-by: Hou Zhiqiang Added

Re: [PATCH 1/1] i2c: designware: reverts "i2c: designware: Add support for AMD I2C controller"

On Fri, Oct 23, 2015 at 01:28:47PM +0800, Ken Xue wrote: > The patch reverts commit a445900c9060 (i2c: designware: Add support for > AMD I2C controller) > > Since kernel starts to support APD(drivers/acpi/acpi_apd.c), there is > no need to get freq from id->driver_data for AMD0010. clkdev is

Re: [GIT PULL] On-demand device probing

On 10/22/2015 09:26 PM, Greg Kroah-Hartman wrote: > On Thu, Oct 22, 2015 at 11:53:31AM -0700, Frank Rowand wrote: >> On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote: >>> >>> >>> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote: But that's moot currently

[Patch V8] i2c: imx: implement bus recovery

Implement bus recovery methods for i2c-imx so we can recover from situations where SCL/SDA are stuck low. Once i2c bus SCL/SDA are stuck low during transfer, config the i2c pinctrl to gpio mode by calling pinctrl sleep set function, and then use GPIO to emulate the i2c protocol to send nine dummy

Re: [GIT PULL] On-demand device probing

On 10/22/2015 11:53 AM, Frank Rowand wrote: > On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote: >> >> >> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote: >>> But that's moot currently because Greg believes that the time spent >>> probing devices at boot time

[PATCH v4 3/5] mfd: intel_quark_i2c_gpio: support devices behind i2c bus

On Intel Galileo Gen2 the GPIO expanders are connected to the i2c bus. For those devices the ACPI table has specific parameters that refer to an actual i2c host controller. Since MFD now copes with that specific configuration we have to provide a necessary information how to distinguish devices in

[PATCH v4 1/5] mfd: core: redo ACPI matching of the children devices

There is at least one board on the market, i.e. Intel Galileo Gen2, that uses _ADR to distinguish the devices under one actual device. Due to this we have to improve the quirk in the MFD core to handle that board. Acked-by: Rafael J. Wysocki Acked-by: Lee Jones

[PATCH v4 4/5] at24: enable ACPI device found on Galileo Gen2

There is a 24c08 chip connected to i2c bus on Intel Galileo Gen2 board. Enable it via ACPI ID INT3499. Signed-off-by: Andy Shevchenko --- drivers/misc/eeprom/at24.c | 22 +++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git

Re: [PATCH v4 0/5] enable I2C devices behind I2C bus on Gen2

> Wolfram, since Lee acknowledged patches 1-3, can you pull them to your tree? So, I picked patches 1-4 to my for-next. Patch 5 is missing an ACK. signature.asc Description: Digital signature

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

Hi Wolfram, On Friday 23 October 2015 14:14:39 Wolfram Sang wrote: > > > :/ Let me know if I can send you debug output. > > > > What's the exact issue ? > > Best report ever: I simply don't get a picture :) No warnings, no > messages. I think we want to make sure my HDMI->DVI converter is

Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports

On Fri, Oct 23, 2015 at 12:16:11PM +0200, Wolfram Sang wrote: > On Fri, Oct 23, 2015 at 11:40:13AM +0300, Mika Westerberg wrote: > > On Thu, Oct 22, 2015 at 02:17:42AM -0700, Dustin Byford wrote: > > > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or > > > device property

Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports

On 10/23/2015 04:40 PM, Mika Westerberg wrote: On Fri, Oct 23, 2015 at 04:13:11PM +0300, Mika Westerberg wrote: On Fri, Oct 23, 2015 at 12:16:11PM +0200, Wolfram Sang wrote: On Fri, Oct 23, 2015 at 11:40:13AM +0300, Mika Westerberg wrote: On Thu, Oct 22, 2015 at 02:17:42AM -0700, Dustin

Re: [PATCH v4 0/5] enable I2C devices behind I2C bus on Gen2

On Fri, 2015-10-23 at 14:38 +0200, Wolfram Sang wrote: > > Wolfram, since Lee acknowledged patches 1-3, can you pull them to > > your tree? > > So, I picked patches 1-4 to my for-next. Patch 5 is missing an ACK. Right. Thanks! -- Andy Shevchenko Intel

Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports

On Fri, Oct 23, 2015 at 04:13:11PM +0300, Mika Westerberg wrote: > On Fri, Oct 23, 2015 at 12:16:11PM +0200, Wolfram Sang wrote: > > On Fri, Oct 23, 2015 at 11:40:13AM +0300, Mika Westerberg wrote: > > > On Thu, Oct 22, 2015 at 02:17:42AM -0700, Dustin Byford wrote: > > > > Although I2C mux

Re: [Patch V8] i2c: imx: implement bus recovery

On Fri, Oct 23, 2015 at 08:28:54PM +0800, Gao Pan wrote: > Implement bus recovery methods for i2c-imx so we can recover from > situations where SCL/SDA are stuck low. > > Once i2c bus SCL/SDA are stuck low during transfer, config the i2c > pinctrl to gpio mode by calling pinctrl sleep set

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

> > :/ Let me know if I can send you debug output. > > What's the exact issue ? Best report ever: I simply don't get a picture :) No warnings, no messages. I think we want to make sure my HDMI->DVI converter is proper, though. > > > .config attached. > > > > That one also probes for me... I

Re: [PATCH v2 2/2] i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver

On Fri, Oct 23, 2015 at 07:52:00PM +0900, Masahiro Yamada wrote: > Add support for on-chip I2C controller used on newer UniPhier SoCs > such as PH1-Pro4, PH1-Pro5, etc. This adapter is equipped with > 8-depth TX/RX FIFOs. > > Signed-off-by: Masahiro Yamada

Re: [Patch V8] i2c: imx: implement bus recovery

On Mon, Oct 19, 2015 at 10:17:02AM +0800, Gao Pan wrote: > Implement bus recovery methods for i2c-imx so we can recover from > situations where SCL/SDA are stuck low. > > Once i2c bus SCL/SDA are stuck low during transfer, config the i2c > pinctrl to gpio mode by calling pinctrl sleep set

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

Hi Wolfram, On Friday 23 October 2015 11:45:00 Wolfram Sang wrote: > > I had CONFIG_DRM_FBDEV_EMULATION disabled. I've then enabled it but also > > merged git://people.freedesktop.org/~airlied/linux next in my branch, > > which probably fixes the problem. > > So, your tree is not strictly

Re: [PATCH 2/3] i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver

2015-10-23 6:06 GMT+09:00 Wolfram Sang : > On Thu, Jul 30, 2015 at 05:12:21PM +0900, Masahiro Yamada wrote: >> Add support for on-chip I2C controller used on newer UniPhier SoCs >> such as PH1-Pro4, PH1-Pro5, etc. This adapter is equipped with >> 8-depth TX/RX FIFOs. >> >>

[PATCH v4 0/5] enable I2C devices behind I2C bus on Gen2

There is a board in the wild, i.e. Intel Galileo Gen2, that has ACPI enumerated devices behind I2C bus. This patch series dedicated to enable those devices. The MFD framework is also updated to cope with interesting implementation of the cell descriptions under ACPI MFD (patch 1). The patches 5

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

On Fri, Oct 23, 2015 at 10:06 AM, Wolfram Sang wrote: >> b9653e9c000dc2ebd9c8712442c659ccd1586e22 from Geert's drivers tree ? On my > > Does that build for you? > > drivers/gpu/drm/drm_fb_helper.c: In function 'restore_fbdev_mode': > drivers/gpu/drm/drm_fb_helper.c:448:5:

Re: [PATCH 3/3] i2c: uniphier: add bindings for UniPhier I2C controllers

2015-10-23 6:00 GMT+09:00 Wolfram Sang : > On Thu, Jul 30, 2015 at 05:12:22PM +0900, Masahiro Yamada wrote: >> Device Tree bindings for two I2C controllers embedded in >> UniPhier SoCs. >> >> Signed-off-by: Masahiro Yamada > > Please split this

Re: [PATCH v2 1/2] i2c: uniphier: add UniPhier FIFO-less I2C driver

On Fri, Oct 23, 2015 at 07:51:59PM +0900, Masahiro Yamada wrote: > Add support for on-chip I2C controller used on old UniPhier SoCs > such as PH1-LD4, PH1-sLD8, etc. This adapter is so simple that > it has no FIFO in it. > > Signed-off-by: Masahiro Yamada Applied

[PATCH v4 2/5] mfd: intel_quark_i2c_gpio: load gpio driver first

On Intel Galileo boards the GPIO expander is connected to i2c bus. Moreover it is able to generate interrupt, but interrupt line is connected to GPIO. That's why we have to have GPIO driver in place when we will probe i2c host with device connected to it. Acked-by: Lee Jones

[PATCH v4 5/5] pwm-pca9685: enable ACPI device found on Galileo Gen2

There is a chip connected to i2c bus on Intel Galileo Gen2 board. Enable it via ACPI ID INT3492. Cc: Thierry Reding Signed-off-by: Andy Shevchenko --- drivers/pwm/Kconfig | 2 +- drivers/pwm/pwm-pca9685.c | 20

Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports

On Fri, Oct 23, 2015 at 11:40:13AM +0300, Mika Westerberg wrote: > On Thu, Oct 22, 2015 at 02:17:42AM -0700, Dustin Byford wrote: > > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or > > device property compatible string match), enumerating I2C client devices > > connected

[PATCH v2 2/2] i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver

Add support for on-chip I2C controller used on newer UniPhier SoCs such as PH1-Pro4, PH1-Pro5, etc. This adapter is equipped with 8-depth TX/RX FIFOs. Signed-off-by: Masahiro Yamada --- Changes in v2: - Delete if-block after platform_get_resource() - Add

Re: [PATCH 1/3] i2c: uniphier: add UniPhier FIFO-less I2C driver

Hi Wolfram, Thanks for your review! 2015-10-23 5:59 GMT+09:00 Wolfram Sang : > On Thu, Jul 30, 2015 at 05:12:20PM +0900, Masahiro Yamada wrote: >> Add support for on-chip I2C controller used on old UniPhier SoCs >> such as PH1-LD4, PH1-sLD8, etc.. This adapter is so simple

[PATCH v2 1/2] i2c: uniphier: add UniPhier FIFO-less I2C driver

Add support for on-chip I2C controller used on old UniPhier SoCs such as PH1-LD4, PH1-sLD8, etc. This adapter is so simple that it has no FIFO in it. Signed-off-by: Masahiro Yamada --- Changes in v2: - Delete if-block after platform_get_resource() - Add

[PATCH v2 0/2] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform

This series adds two I2C controller drivers. (they are completely different IPs.) The first one is a very simple FIFO-less I2C controller, which is used on some older UniPhier SoCs. The other one is higher-performance I2C controller with TX/RX FIFO, used on newer UniPhier SoCs. Changes in v2:

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

> I had CONFIG_DRM_FBDEV_EMULATION disabled. I've then enabled it but also > merged git://people.freedesktop.org/~airlied/linux next in my branch, which > probably fixes the problem. So, your tree is not strictly renesas-drivers-2015-10-13-v4.3-rc5? > > I fixed it locally and will see if I

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

> - error = true; > + return ret; Yup, did that, too :) signature.asc Description: Digital signature

Re: [GIT PULL] On-demand device probing

On Fri, Oct 23, 2015 at 10:45 AM, Tim Bird wrote: > On 10/22/2015 11:53 AM, Frank Rowand wrote: >> On 10/22/2015 7:44 AM, Greg Kroah-Hartman wrote: >>> >>> >>> On Thu, Oct 22, 2015 at 11:05:11AM +0200, Tomeu Vizoso wrote: But that's moot

Re: [PATCH v4 4/5] at24: enable ACPI device found on Galileo Gen2

Hi, On Fri, Oct 23, 2015 at 4:16 AM, Andy Shevchenko wrote: > There is a 24c08 chip connected to i2c bus on Intel Galileo Gen2 board. Enable > it via ACPI ID INT3499. I'm looking to do something similar with a 24C02 and would like to know if there is an ID

Re: [PATCH] i2c: mediatek: add i2c resume support

On Tue, Oct 06, 2015 at 05:22:56PM +0800, Eddie Huang wrote: > From: Liguo Zhang > > mt65xx i2c controller initial setting will be cleared after system suspend, > so we should init mt65xx i2c controller again when system resume. > > Signed-off-by: Liguo Zhang

Re: [PATCH] i2c: i801: Add support for Intel Broxton

On Thu, Oct 22, 2015 at 05:16:58PM +0300, Jarkko Nikula wrote: > This patch adds the SMBUS PCI ID of Intel Broxton. > > Signed-off-by: Jarkko Nikula Applied to for-next, thanks! signature.asc Description: Digital signature

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

On Sat, Oct 17, 2015 at 09:52:27PM +0300, Vladimir Zapolskiy wrote: > If common clock framework is configured, the driver generates a warning, > which is fixed by this change: > > WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:727 > clk_core_enable+0x2c/0xa4() > Modules linked in: >

Re: [PATCH 2/2] i2c: designware: enable High-speed mode for pcidrv

> > Should it (ACPI walk) be done in PCI case as well? If so, then it needs > > to be done up to i2c-core. There you may adjust the bus speed whenever > > slave device is enumerated. > > > I think the "ACPI walk for bus speed" also works for PCI case. It'll > be good to do this in i2c-core. > By

Re: [PATCH] i2c: i801: Add support for Intel DNV

On Tue, Oct 13, 2015 at 03:41:39PM +0300, Mika Westerberg wrote: > Intel DNV SoC has the same legacy SMBus host controller than Intel > Sunrisepoint PCH. It also has same iTCO watchdog on the bus. > > Add DNV PCI ID to the list of supported devices. > > Signed-off-by: Mika Westerberg

[PATCH v5 2/2] i2c: add ACPI support for I2C mux ports

Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or device property compatible string match), enumerating I2C client devices connected through an I2C mux needs a little extra work. This change implements a method for describing an I2C device hierarchy that includes mux devices

[PATCH v5 0/2] i2c: acpi: scan ACPI enumerated I2C mux channels

v5: - rebased on i2c/for-next (Jarkko, Wolfram) - include acpi.h in designware drivers (Mika) - remove return from void stub function (Mika) - add acks and tested-by from Mika v4: - Moved the acpi_preset_companion() stub to a separate patch. - Moved ACPI companion set from i2c-core to i801, ismt,

[PATCH] driver/i2c: Add API to add new I2C device without registering

Split existing API i2c_new_device(), i2c_new_probed_device() into two halves. The first half creates new i2c devices and the second half calls device_register(). It allows additional work to be done before registering the device. Signed-off-by: York Sun CC: Wolfram Sang

[PATCH v5 1/2] acpi: add acpi_preset_companion() stub

Add a stub for acpi_preset_companion(). Fixes build failures when acpi_preset_companion() is used and CONFIG_ACPI is not set. Acked-by: Mika Westerberg Signed-off-by: Dustin Byford --- include/linux/acpi.h | 5 + 1 file changed,

Re: [PATCH] i2c: sirf: tune the divider to make i2c bus freq more accurate

On Wed, Sep 09, 2015 at 10:30:32AM +, Barry Song wrote: > From: Guoying Zhang > > In prima2 and atlas7, due to some hardware design issue. we > need to adjust the divider ratio a little according to i2c > bus frequency ranges. > Since i2c is open drain interface that

Re: [PATCH] i2c: i2c-imx: Use -ENXIO as error in the NACK case

On Thu, Oct 22, 2015 at 02:41:20PM -0200, Fabio Estevam wrote: > According to Documentation/i2c/fault-codes the response to a bus NACK > should be -ENXIO, so fix the error code. > > This change is similar to commit 6ff4b1051632 ("i2c: rcar: fix NACK > error code"). > > Signed-off-by: Fabio

Re: [PATCH] i2c: pnx: fix warnings caused by enabling unprepared clock

> Applied to for-next with your updated commit message, thanks! Actually, applied to for-current, thanks! signature.asc Description: Digital signature

Re: [PATCH] i2c: tegra: drop duplicated code for assigning algo

On Tue, Oct 20, 2015 at 05:40:46PM +0200, Wolfram Sang wrote: > > @@ -825,7 +825,6 @@ static int tegra_i2c_probe(struct platform_device *pdev) > > i2c_dev->adapter.class = I2C_CLASS_DEPRECATED; > > strlcpy(i2c_dev->adapter.name, "Tegra I2C adapter", > >

Re: [PATCH] i2c-dev: Fix typo in ioctl name reference

> > > -#define I2C_RDRW_IOCTL_MAX_MSGS 42 > > > +#define I2C_RDWR_IOCTL_MAX_MSGS 42 > > > +/* Originally defined with a typo, keep if for now for compatibility */ > > > > I would drop the 'for now' and keep it forever. A define doesn't hurt > > and if it increases backwards compatibility, why

Re: [PATCH RFT] i2c: au1550: Convert to devm_kzalloc and devm_ioremap_resource

On Tue, Jun 09, 2015 at 03:52:49PM +0800, Axel Lin wrote: > Use devm_* APIs to simplify the code. > > Signed-off-by: Axel Lin Applied to for-next with Manuel's Tested-by, thanks! signature.asc Description: Digital signature

Re: [PATCH] i2c-dev: Fix I2C_SLAVE ioctl comment

On Fri, Sep 11, 2015 at 11:27:18AM +0200, Jean Delvare wrote: > The first part of the comment is wrong since November 2007, delete it. > > The second part of the comment is related to I2C_PEC, not I2C_SLAVE, so > move it where it belongs. > > Signed-off-by: Jean Delvare > Cc:

Re: [PATCH v4 1/2] acpi: add acpi_preset_companion() stub

On Thu, Oct 22, 2015 at 02:17:41AM -0700, Dustin Byford wrote: > Add a stub for acpi_preset_companion(). Fixes build failures when > acpi_preset_companion() is used and CONFIG_ACPI is not set. > > Signed-off-by: Dustin Byford > --- > include/linux/acpi.h | 6 ++

Re: [PATCH 5/9] i2c: rcar: init new messages in irq

> Do you have a Koelsch board now ? Could you try Nope, I only have Lager. I'd be surprised if it really was a Koelsch only issue, though... > b9653e9c000dc2ebd9c8712442c659ccd1586e22 from Geert's drivers tree ? On my Does that build for you? drivers/gpu/drm/drm_fb_helper.c: In function

[PATCH V6 2/6] watchdog: Add support for Freescale Layerscape platforms

From: Shaohui Xie Modify watchdog/Kconfig file to support Layerscape platforms. Signed-off-by: Shaohui Xie Signed-off-by: Hou Zhiqiang Acked-by: Guenter Roeck --- V6: - Remove a Signed-off. V5:

[PATCH V6 4/6] arm64/ls1043a: add DTS for Freescale LS1043A SoC

From: Mingkai Hu LS1043a is an SoC with 4 ARMv8 A53 cores and most other IP blocks similar to LS1021a which complies to Chassis 2.1 spec. Following levels of DTSI/DTS files have been created for the LS1043A SoC family: - fsl-ls1043a.dtsi: DTS-Include file for FSL

[PATCH V6 5/6] clk: qoriq: Add ls1043a support.

From: Hou Zhiqiang Signed-off-by: Hou Zhiqiang Acked-by: Stephen Boyd --- V6: V5 V4 V3 V2 - No change. drivers/clk/clk-qoriq.c | 38 ++ 1 file changed, 38 insertions(+) diff --git

[PATCH V6 1/6] i2c: Add i2c support to Freescale Layerscape platforms

From: Shaohui Xie Modify the I2C_IMX config to support to Layerscape platforms. Signed-off-by: Shaohui Xie Signed-off-by: Hou Zhiqiang --- V6: - Remove some Signed-off and add the author's. V5: V4 V3 V2 - No

[PATCH V6 6/6] dts/ls1043a: add LS1043ARDB board support

From: Shaohui Xie Signed-off-by: Shaohui Xie Signed-off-by: Mingkai Hu Signed-off-by: Wenbin Song Signed-off-by: Hou Zhiqiang --- V6: V5 V4 V3 - No change. V2:

Re: [PATCH 1/1] i2c: designware: reverts "i2c: designware: Add support for AMD I2C controller"

On Fri, Oct 23, 2015 at 01:28:47PM +0800, Ken Xue wrote: > The patch reverts commit a445900c9060 (i2c: designware: Add support for > AMD I2C controller) > > Since kernel starts to support APD(drivers/acpi/acpi_apd.c), there is > no need to get freq from id->driver_data for AMD0010. clkdev is

Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports

On Thu, Oct 22, 2015 at 02:17:42AM -0700, Dustin Byford wrote: > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or > device property compatible string match), enumerating I2C client devices > connected through an I2C mux needs a little extra work. > > This change implements