On Thu, Dec 10, 2015 at 03:56:27PM +0200, Jarkko Nikula wrote:
> On 12/10/2015 02:59 PM, Andy Shevchenko wrote:
> >On Thu, 2015-12-10 at 13:48 +0200, Jarkko Nikula wrote:
> >>I believe i2c-designware-baytrail.c doesn't have strict dependency
> >>that
> >>Intel SoC IOSF Sideband support must be
> After that, introduce a new property 'linux,i2c-retry-count' to be used
> as retries field in struct i2c_adapter.
Hmm, to be honest, I always have difficulties with this "retries"
parameter; to me "try x milliseconds" makes more sense than "try 5
times". It is there for ages, so we have to
> >> +static int rk3x_i2c_v0_calc_divs(unsigned long clk_rate, unsigned long
> >> scl_rate,
> >> +unsigned long scl_rise_ns,
> >> +unsigned long scl_fall_ns,
> >> +unsigned long sda_fall_ns,
>
>
On Mon, Jan 04, 2016 at 09:15:37AM -0200, Fabio Estevam wrote:
> These multi-lines comments do not follow the standard kernel coding
> style. In fact, they are not useful comments, so get rid of them.
>
> Signed-off-by: Fabio Estevam
Applied to for-next, thanks!
On Tue, Dec 15, 2015 at 03:55:53PM -0600, Suravee Suthikulpanit wrote:
> Add device HID AMDI0510 to match the I2C controlers on AMD Seattle platform
>
> Signed-off-by: Suravee Suthikulpanit
Applied to for-next, thanks!
signature.asc
Description: Digital
On Wed, Dec 02, 2015 at 05:52:38PM +0800, Gao Pan wrote:
> In i2c_imx_dma_xfer(), when dmaengine_prep_slave_single() returns
> NULL, the context goto label err_desc and then return. However,
> the memory allocated by dmaengine_prep_slave_single() has not been
> freed yet, which leads to resource
On Mon, Jan 04, 2016 at 02:15:37PM +0800, Liguo Zhang wrote:
> Add a dt binding for the MT2701 soc.
>
> Signed-off-by: Liguo Zhang
This should probably go with the other patch via arm-soc, or?
In that case:
Acked-by: Wolfram Sang
signature.asc
Enable power management. This patch enables the clocks
before transfer and disables after the transfer.
Signed-off-by: Shubhrajyoti Datta
---
drivers/i2c/busses/i2c-xiic.c | 86 +---
1 files changed, 79 insertions(+), 7 deletions(-)
Add clock description for i2c-xiic
Signed-off-by: Shubhrajyoti Datta
---
Documentation/devicetree/bindings/i2c/i2c-xiic.txt |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-xiic.txt
On 23/12/15 09:34, Ken Xue wrote:
> On Tue, 2015-12-15 at 16:59 +0200, Mika Westerberg wrote:
>> On Tue, Dec 15, 2015 at 08:52:19AM -0600, Suravee Suthikulpanit wrote:
> During test, I2C bus should run in different "ConnectionSpeed" of
> device.
>
> That means windows driver can modify I2C bus
On Tue, Nov 17, 2015 at 05:15:22PM +0530, Sricharan R wrote:
> qup_wait_writeready waits only on a output fifo empty event.
> Change the same function to accept the event and data length
> to wait as parameters. This way the same function can be used for
> timeouts in other places as well.
>
>
Stephen,
> > After merging the i2c tree, today's linux-next build (powerpc
> > ppc44x_defconfig) failed like this:
Oops, yes.
> > /* Bus timings (in ns) for bit-banging */
> > -static struct i2c_timings {
> > +static struct ibm_i2c_timings {
I changed it to ibm_iic_timings for consistency
From: Xu Jianqun
There is a requirement from pmic device, which is on the i2c bus,
that the pmic needs to be called earlier then devices powered by
the outputs of the pmic, if not, the devices maybe fail to probe.
For example, a pmic on i2c0, and touchscreen device on
2016-01-02 21:50 GMT+01:00 Wolfram Sang :
> On Fri, Dec 11, 2015 at 02:55:10PM +0100, Bartosz Golaszewski wrote:
>> 2015-12-11 13:08 GMT+01:00 Wolfram Sang :
>> > On Wed, Dec 02, 2015 at 11:25:17AM +0100, Bartosz Golaszewski wrote:
>> >> Chips from the
On Mon, Jan 04, 2016 at 01:20:34PM +0530, Shubhrajyoti Datta wrote:
> Add clock description for i2c-xiic
>
> Signed-off-by: Shubhrajyoti Datta
> ---
> Documentation/devicetree/bindings/i2c/i2c-xiic.txt |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
These multi-lines comments do not follow the standard kernel coding
style. In fact, they are not useful comments, so get rid of them.
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Rebased against latest tree
drivers/i2c/busses/i2c-imx.c | 12
1 file
Hi Jianqun,
Am Dienstag, 5. Januar 2016, 11:02:18 schrieb jianqun.xu:
> From: Xu Jianqun
>
> There is a requirement from pmic device, which is on the i2c bus,
> that the pmic needs to be called earlier then devices powered by
> the outputs of the pmic, if not, the devices
Hi Heiko:
在 05/01/2016 15:02, Heiko Stuebner 写道:
Hi Jianqun,
Am Dienstag, 5. Januar 2016, 11:02:18 schrieb jianqun.xu:
From: Xu Jianqun
There is a requirement from pmic device, which is on the i2c bus,
that the pmic needs to be called earlier then devices powered by
Hi, Heiko:
On 2016年01月05日 15:02, Heiko Stuebner wrote:
> Hi Jianqun,
>
> Am Dienstag, 5. Januar 2016, 11:02:18 schrieb jianqun.xu:
>> From: Xu Jianqun
>>
>> There is a requirement from pmic device, which is on the i2c bus,
>> that the pmic needs to be called earlier then
From: Peter Rosin
Instead of checking for i2c parent adapters for every lock/unlock, simply
override the locking for muxes to always lock/unlock the parent adapter
directly.
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-core.c | 21 +++--
From: Peter Rosin
Add i2c_lock_bus() and i2c_unlock_bus(), which call the new lock_bus and
unlock_bus ops in the adapter. These funcs/ops take an additional flags
argument that indicates for what purpose the adapter is locked.
There are two flags, I2C_LOCK_ADAPTER and
From: Peter Rosin
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pca9541.c | 82 +++--
1 file changed, 15 insertions(+), 67 deletions(-)
diff --git a/drivers/i2c/muxes/i2c-mux-pca9541.c
From: Peter Rosin
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pca954x.c | 32 ++--
1 file changed, 10 insertions(+), 22 deletions(-)
diff --git a/drivers/i2c/muxes/i2c-mux-pca954x.c
From: Peter Rosin
Hi!
I have a pair of boards with this i2c topology:
GPIO ---| -- BAT1
| v /
I2C -+--B---+ MUX
| \
EEPROM -- BAT2
(B
On 2016-01-04 16:19, Lars-Peter Clausen wrote:
> On 01/04/2016 04:10 PM, Peter Rosin wrote:
>> From: Peter Rosin
>>
>> Signed-off-by: Peter Rosin
>
> It would be quite good if the commit messaged said why it is now safe to
> remove the workaround.
Right, hmm,
From: Peter Rosin
The initial core mux structure starts off small with only the parent
adapter pointer, which all muxes have, and a priv pointer for mux
driver private data.
Add i2c_mux_alloc function to unify the creation of a mux.
Where appropriate, pass around the mux core
Hi Peter,
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup
Hi Peter,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup-and-locking
Hi Peter,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup-and-locking
From: Peter Rosin
The dev pointer is readily available in the mux core struct, no point in
keeping multiple copies around.
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-mux.c | 24
From: Peter Rosin
All muxes have slave side adapters, many have some arbitrary number of
them. Handle this in the mux core, so that drivers are simplified.
Add i2c_mux_reserve_adapter that can be used when it is known in advance
how many child adapters that is to be added. This
From: Peter Rosin
The mux select and deselect ops are common to the mux most of the time,
so store the ops in the mux core.
Change the select and deselect op to work in terms of the mux core instead
of the child adapter. No driver uses the child adapter anyway, and if it
is
Hi Andy,
On 12/23/2015 12:27 PM, Andy Shevchenko wrote:
diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c
>b/drivers/i2c/busses/i2c-designware-platdrv.c
>index 8ffc36b..04edd09 100644
>--- a/drivers/i2c/busses/i2c-designware-platdrv.c
>+++ b/drivers/i2c/busses/i2c-designware-platdrv.c
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 SSCN and FFCN ACPI methods, which can be used
to directly
From: Peter Rosin
With a i2c topology like the following
GPIO ---| -- BAT1
| v /
I2C -+--+ MUX
| \
EEPROM -- BAT2
there is a locking
On 01/04/2016 04:10 PM, Peter Rosin wrote:
> From: Peter Rosin
>
> Signed-off-by: Peter Rosin
It would be quite good if the commit messaged said why it is now safe to
remove the workaround.
--
To unsubscribe from this list: send the line "unsubscribe
On 01/04/2016 07:10 AM, Peter Rosin wrote:
From: Peter Rosin
The initial core mux structure starts off small with only the parent
adapter pointer, which all muxes have, and a priv pointer for mux
driver private data.
Add i2c_mux_alloc function to unify the creation of a mux.
Hi Peter,
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup
Hi Peter,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup-and-locking
Hi Peter,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.4-rc8 next-20160104]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Rosin/i2c-mux-cleanup-and-locking
On Mon, Jan 04, 2016 at 09:17:35AM -0600, Suravee Suthikulpanit wrote:
> 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
https://github.com/0day-ci/linux
Peter-Rosin/i2c-mux-cleanup-and-locking-update/20160104-231355
8627e12bd6d3fc7506656f026a23afae52d12c73 i2c: pca954x: get rid of the i2c
deadlock workaround
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c:845:18: warning: assignment makes
pointer from integer
On Sat, Jan 2, 2016 at 11:21 PM, Wolfram Sang wrote:
> On Sun, Dec 27, 2015 at 04:57:48PM +0200, Andy Shevchenko wrote:
>> On Wed, Dec 23, 2015 at 9:18 PM, Akshay Bhat wrote:
>> > "at" is not a valid vendor prefix, correcting the same to "atmel"
>> >
43 matches
Mail list logo