* [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
@ 2016-04-26 6:27 ` Dirk Behme
0 siblings, 0 replies; 7+ messages in thread
From: Dirk Behme @ 2016-04-26 6:27 UTC (permalink / raw)
To: Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
From: Oleksij Rempel <linux@rempel-privat.de>
Documentation/timers/timers-howto.txt recommends to use
usleep_range on delays > 10usec. According to my test results
with Neonode zForce touchscreen driver, usleep_range indeed
reduces CPU load.
Stats collected with "./perf record -a -g -F 1000 sleep 10"
i2c-imx with udelay(50):
34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
---irq_thread
|--33.75%--irq_thread_fn
| |--19.27%--0x7f08a878
| | i2c_master_recv
| | i2c_transfer
| | __i2c_transfer
| | i2c_imx_xfer
| | |--11.71%--i2c_imx_trx_complete
| | |--5.70%--i2c_imx_start <<<<----------------
| | | |--5.38%--__timer_const_udelay
| | | | __timer_delay
| | | | --5.07%--read_current_timer
i2c-imx with usleep_range(50,100)
29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
---irq_thread
|--28.89%--irq_thread_fn
| |--17.21%--0x7f08a878
| | i2c_master_recv
| | |--17.14%--i2c_transfer
| | | __i2c_transfer
| | | i2c_imx_xfer
| | | |--14.29%--i2c_imx_trx_complete
| | | |--1.42%--i2c_imx_start <<<<----------
| | | | |--0.71%--usleep_range
| | | | |--0.53%--i2c_imx_bus_busy
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
---
drivers/i2c/busses/i2c-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
index 1ca7ef2..1844bc9 100644
--- a/drivers/i2c/busses/i2c-imx.c
+++ b/drivers/i2c/busses/i2c-imx.c
@@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
/* Wait controller to be stable */
- udelay(50);
+ usleep_range(50, 150);
/* Start I2C transaction */
temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
--
2.8.0
^ permalink raw reply related [flat|nested] 7+ messages in thread* [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
@ 2016-04-26 6:27 ` Dirk Behme
0 siblings, 0 replies; 7+ messages in thread
From: Dirk Behme @ 2016-04-26 6:27 UTC (permalink / raw)
To: Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
From: Oleksij Rempel <linux@rempel-privat.de>
Documentation/timers/timers-howto.txt recommends to use
usleep_range on delays > 10usec. According to my test results
with Neonode zForce touchscreen driver, usleep_range indeed
reduces CPU load.
Stats collected with "./perf record -a -g -F 1000 sleep 10"
i2c-imx with udelay(50):
34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
---irq_thread
|--33.75%--irq_thread_fn
| |--19.27%--0x7f08a878
| | i2c_master_recv
| | i2c_transfer
| | __i2c_transfer
| | i2c_imx_xfer
| | |--11.71%--i2c_imx_trx_complete
| | |--5.70%--i2c_imx_start <<<<----------------
| | | |--5.38%--__timer_const_udelay
| | | | __timer_delay
| | | | --5.07%--read_current_timer
i2c-imx with usleep_range(50,100)
29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
---irq_thread
|--28.89%--irq_thread_fn
| |--17.21%--0x7f08a878
| | i2c_master_recv
| | |--17.14%--i2c_transfer
| | | __i2c_transfer
| | | i2c_imx_xfer
| | | |--14.29%--i2c_imx_trx_complete
| | | |--1.42%--i2c_imx_start <<<<----------
| | | | |--0.71%--usleep_range
| | | | |--0.53%--i2c_imx_bus_busy
Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
---
drivers/i2c/busses/i2c-imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
index 1ca7ef2..1844bc9 100644
--- a/drivers/i2c/busses/i2c-imx.c
+++ b/drivers/i2c/busses/i2c-imx.c
@@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
/* Wait controller to be stable */
- udelay(50);
+ usleep_range(50, 150);
/* Start I2C transaction */
temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
--
2.8.0
^ permalink raw reply related [flat|nested] 7+ messages in thread* Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
2016-04-26 6:27 ` Dirk Behme
@ 2016-04-26 11:02 ` Vladimir Zapolskiy
-1 siblings, 0 replies; 7+ messages in thread
From: Vladimir Zapolskiy @ 2016-04-26 11:02 UTC (permalink / raw)
To: Dirk Behme, Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
Hi Dirk,
On 26.04.2016 09:27, Dirk Behme wrote:
> From: Oleksij Rempel <linux@rempel-privat.de>
>
> Documentation/timers/timers-howto.txt recommends to use
> usleep_range on delays > 10usec. According to my test results
> with Neonode zForce touchscreen driver, usleep_range indeed
> reduces CPU load.
>
> Stats collected with "./perf record -a -g -F 1000 sleep 10"
>
> i2c-imx with udelay(50):
> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
> ---irq_thread
> |--33.75%--irq_thread_fn
> | |--19.27%--0x7f08a878
> | | i2c_master_recv
> | | i2c_transfer
> | | __i2c_transfer
> | | i2c_imx_xfer
> | | |--11.71%--i2c_imx_trx_complete
> | | |--5.70%--i2c_imx_start <<<<----------------
> | | | |--5.38%--__timer_const_udelay
> | | | | __timer_delay
> | | | | --5.07%--read_current_timer
>
> i2c-imx with usleep_range(50,100)
> 29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
> ---irq_thread
> |--28.89%--irq_thread_fn
> | |--17.21%--0x7f08a878
> | | i2c_master_recv
> | | |--17.14%--i2c_transfer
> | | | __i2c_transfer
> | | | i2c_imx_xfer
> | | | |--14.29%--i2c_imx_trx_complete
> | | | |--1.42%--i2c_imx_start <<<<----------
> | | | | |--0.71%--usleep_range
> | | | | |--0.53%--i2c_imx_bus_busy
>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
missing your Signed-off-by.
Reviewed-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> ---
> drivers/i2c/busses/i2c-imx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 1ca7ef2..1844bc9 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
> imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
>
> /* Wait controller to be stable */
> - udelay(50);
> + usleep_range(50, 150);
>
> /* Start I2C transaction */
> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
>
--
With best wishes,
Vladimir
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
@ 2016-04-26 11:02 ` Vladimir Zapolskiy
0 siblings, 0 replies; 7+ messages in thread
From: Vladimir Zapolskiy @ 2016-04-26 11:02 UTC (permalink / raw)
To: Dirk Behme, Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
Hi Dirk,
On 26.04.2016 09:27, Dirk Behme wrote:
> From: Oleksij Rempel <linux@rempel-privat.de>
>
> Documentation/timers/timers-howto.txt recommends to use
> usleep_range on delays > 10usec. According to my test results
> with Neonode zForce touchscreen driver, usleep_range indeed
> reduces CPU load.
>
> Stats collected with "./perf record -a -g -F 1000 sleep 10"
>
> i2c-imx with udelay(50):
> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
> ---irq_thread
> |--33.75%--irq_thread_fn
> | |--19.27%--0x7f08a878
> | | i2c_master_recv
> | | i2c_transfer
> | | __i2c_transfer
> | | i2c_imx_xfer
> | | |--11.71%--i2c_imx_trx_complete
> | | |--5.70%--i2c_imx_start <<<<----------------
> | | | |--5.38%--__timer_const_udelay
> | | | | __timer_delay
> | | | | --5.07%--read_current_timer
>
> i2c-imx with usleep_range(50,100)
> 29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
> ---irq_thread
> |--28.89%--irq_thread_fn
> | |--17.21%--0x7f08a878
> | | i2c_master_recv
> | | |--17.14%--i2c_transfer
> | | | __i2c_transfer
> | | | i2c_imx_xfer
> | | | |--14.29%--i2c_imx_trx_complete
> | | | |--1.42%--i2c_imx_start <<<<----------
> | | | | |--0.71%--usleep_range
> | | | | |--0.53%--i2c_imx_bus_busy
>
> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
missing your Signed-off-by.
Reviewed-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> ---
> drivers/i2c/busses/i2c-imx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 1ca7ef2..1844bc9 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
> imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
>
> /* Wait controller to be stable */
> - udelay(50);
> + usleep_range(50, 150);
>
> /* Start I2C transaction */
> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
>
--
With best wishes,
Vladimir
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
2016-04-26 11:02 ` Vladimir Zapolskiy
@ 2016-04-26 12:22 ` Dirk Behme
-1 siblings, 0 replies; 7+ messages in thread
From: Dirk Behme @ 2016-04-26 12:22 UTC (permalink / raw)
To: Vladimir Zapolskiy, Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
On 26.04.2016 13:02, Vladimir Zapolskiy wrote:
> Hi Dirk,
>
> On 26.04.2016 09:27, Dirk Behme wrote:
>> From: Oleksij Rempel <linux@rempel-privat.de>
>>
>> Documentation/timers/timers-howto.txt recommends to use
>> usleep_range on delays > 10usec. According to my test results
>> with Neonode zForce touchscreen driver, usleep_range indeed
>> reduces CPU load.
>>
>> Stats collected with "./perf record -a -g -F 1000 sleep 10"
>>
>> i2c-imx with udelay(50):
>> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
>> ---irq_thread
>> |--33.75%--irq_thread_fn
>> | |--19.27%--0x7f08a878
>> | | i2c_master_recv
>> | | i2c_transfer
>> | | __i2c_transfer
>> | | i2c_imx_xfer
>> | | |--11.71%--i2c_imx_trx_complete
>> | | |--5.70%--i2c_imx_start <<<<----------------
>> | | | |--5.38%--__timer_const_udelay
>> | | | | __timer_delay
>> | | | | --5.07%--read_current_timer
>>
>> i2c-imx with usleep_range(50,100)
>> 29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
>> ---irq_thread
>> |--28.89%--irq_thread_fn
>> | |--17.21%--0x7f08a878
>> | | i2c_master_recv
>> | | |--17.14%--i2c_transfer
>> | | | __i2c_transfer
>> | | | i2c_imx_xfer
>> | | | |--14.29%--i2c_imx_trx_complete
>> | | | |--1.42%--i2c_imx_start <<<<----------
>> | | | | |--0.71%--usleep_range
>> | | | | |--0.53%--i2c_imx_bus_busy
>>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> missing your Signed-off-by.
>
> Reviewed-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
>
>> ---
>> drivers/i2c/busses/i2c-imx.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
>> index 1ca7ef2..1844bc9 100644
>> --- a/drivers/i2c/busses/i2c-imx.c
>> +++ b/drivers/i2c/busses/i2c-imx.c
>> @@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
>> imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
>>
>> /* Wait controller to be stable */
>> - udelay(50);
>> + usleep_range(50, 150);
>>
>> /* Start I2C transaction */
>> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
>>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
@ 2016-04-26 12:22 ` Dirk Behme
0 siblings, 0 replies; 7+ messages in thread
From: Dirk Behme @ 2016-04-26 12:22 UTC (permalink / raw)
To: Vladimir Zapolskiy, Wolfram Sang, linux-i2c; +Cc: linux-kernel, Oleksij Rempel
On 26.04.2016 13:02, Vladimir Zapolskiy wrote:
> Hi Dirk,
>
> On 26.04.2016 09:27, Dirk Behme wrote:
>> From: Oleksij Rempel <linux@rempel-privat.de>
>>
>> Documentation/timers/timers-howto.txt recommends to use
>> usleep_range on delays > 10usec. According to my test results
>> with Neonode zForce touchscreen driver, usleep_range indeed
>> reduces CPU load.
>>
>> Stats collected with "./perf record -a -g -F 1000 sleep 10"
>>
>> i2c-imx with udelay(50):
>> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
>> ---irq_thread
>> |--33.75%--irq_thread_fn
>> | |--19.27%--0x7f08a878
>> | | i2c_master_recv
>> | | i2c_transfer
>> | | __i2c_transfer
>> | | i2c_imx_xfer
>> | | |--11.71%--i2c_imx_trx_complete
>> | | |--5.70%--i2c_imx_start <<<<----------------
>> | | | |--5.38%--__timer_const_udelay
>> | | | | __timer_delay
>> | | | | --5.07%--read_current_timer
>>
>> i2c-imx with usleep_range(50,100)
>> 29.08% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
>> ---irq_thread
>> |--28.89%--irq_thread_fn
>> | |--17.21%--0x7f08a878
>> | | i2c_master_recv
>> | | |--17.14%--i2c_transfer
>> | | | __i2c_transfer
>> | | | i2c_imx_xfer
>> | | | |--14.29%--i2c_imx_trx_complete
>> | | | |--1.42%--i2c_imx_start <<<<----------
>> | | | | |--0.71%--usleep_range
>> | | | | |--0.53%--i2c_imx_bus_busy
>>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> missing your Signed-off-by.
>
> Reviewed-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
>
>> ---
>> drivers/i2c/busses/i2c-imx.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
>> index 1ca7ef2..1844bc9 100644
>> --- a/drivers/i2c/busses/i2c-imx.c
>> +++ b/drivers/i2c/busses/i2c-imx.c
>> @@ -525,7 +525,7 @@ static int i2c_imx_start(struct imx_i2c_struct *i2c_imx)
>> imx_i2c_write_reg(i2c_imx->hwdata->i2cr_ien_opcode, i2c_imx, IMX_I2C_I2CR);
>>
>> /* Wait controller to be stable */
>> - udelay(50);
>> + usleep_range(50, 150);
>>
>> /* Start I2C transaction */
>> temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
>>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50)
2016-04-26 6:27 ` Dirk Behme
(?)
(?)
@ 2016-04-26 21:35 ` Wolfram Sang
-1 siblings, 0 replies; 7+ messages in thread
From: Wolfram Sang @ 2016-04-26 21:35 UTC (permalink / raw)
To: Dirk Behme; +Cc: linux-i2c, linux-kernel, Oleksij Rempel
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Tue, Apr 26, 2016 at 08:27:46AM +0200, Dirk Behme wrote:
> From: Oleksij Rempel <linux@rempel-privat.de>
>
> Documentation/timers/timers-howto.txt recommends to use
> usleep_range on delays > 10usec. According to my test results
> with Neonode zForce touchscreen driver, usleep_range indeed
> reduces CPU load.
>
> Stats collected with "./perf record -a -g -F 1000 sleep 10"
>
> i2c-imx with udelay(50):
> 34.19% 0.00% irq/220-Neonode [kernel.kallsyms] [k] irq_thread
> ---irq_thread
> |--33.75%--irq_thread_fn
> | |--19.27%--0x7f08a878
> | | i2c_master_recv
> | | i2c_transfer
> | | __i2c_transfer
> | | i2c_imx_xfer
> | | |--11.71%--i2c_imx_trx_complete
Reworded $subject to match code and applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-04-26 21:35 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-26 6:27 [PATCH] i2c: imx: use usleep_range(50,100) instead of udelay(50) Dirk Behme
2016-04-26 6:27 ` Dirk Behme
2016-04-26 11:02 ` Vladimir Zapolskiy
2016-04-26 11:02 ` Vladimir Zapolskiy
2016-04-26 12:22 ` Dirk Behme
2016-04-26 12:22 ` Dirk Behme
2016-04-26 21:35 ` Wolfram Sang
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.