From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Michail Georgios Etairidis <m.etairidis@beck-ipc.com>
Cc: lst@pengutronix.de, linux-i2c@vger.kernel.org,
kernel@pengutronix.de, Fugang Duan <B38611@freescale.com>,
Yuan Yao <yao.yuan@freescale.com>
Subject: Re: [PATCH] i2c: i2c-imx: Use correct function to write to register
Date: Mon, 19 Jun 2017 20:54:16 +0200 [thread overview]
Message-ID: <20170619185416.owrkfcbvutbhdrmo@pengutronix.de> (raw)
In-Reply-To: <681500CE65202E47A192754B01DAB4671B16747E36@SDE12.beckipc.net>
On Fri, Jun 09, 2017 at 03:28:12PM +0200, Michail Georgios Etairidis wrote:
> The i2c-imx driver incorrectly uses readb()/writeb() to read and write to the appropriate registers when performing a repeated start. The appropriate imx_i2c_read_reg()/imx_i2c_write_reg() functions should be used instead. Performing a repeated start results in a kernel panic.
please limit lines in the commit to 76 chars.
> I am resubmitting this patch as the previous one was erroneous. This patch is based on the current upstream kernel code.
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index 95ed171..54a47b4 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -734,9 +734,9 @@ static int i2c_imx_dma_read(struct imx_i2c_struct *i2c_imx,
> * the first read operation, otherwise the first read cost
> * one extra clock cycle.
> */
> - temp = readb(i2c_imx->base + IMX_I2C_I2CR);
> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> temp |= I2CR_MTX;
> - writeb(temp, i2c_imx->base + IMX_I2C_I2CR);
> + imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
These were introduced by commit ce1a78840ff7a authored by Yao Yuan.
> }
> msgs->buf[msgs->len-1] = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2DR);
>
> @@ -857,9 +857,9 @@ static int i2c_imx_read(struct imx_i2c_struct *i2c_imx, struct i2c_msg *msgs, bo
> * the first read operation, otherwise the first read cost
> * one extra clock cycle.
> */
> - temp = readb(i2c_imx->base + IMX_I2C_I2CR);
> + temp = imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
> temp |= I2CR_MTX;
> - writeb(temp, i2c_imx->base + IMX_I2C_I2CR);
> + imx_i2c_write_reg(temp, i2c_imx, IMX_I2C_I2CR);
These were introduced by commit 054b62d9f25c9 authored by Fugang Duan.
I added these two people to Cc:, maybe they are still at Freescale/NXP
and can comment.
imx_i2c_read_reg(i2c_imx, IMX_I2C_I2CR);
results in
readb(i2c_imx->base + (reg << i2c_imx->hwdata->regshift));
where .regshift is 2 for imx and 0 for vf610. So the patch makes a
difference on the former platforms only.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2017-06-19 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 13:28 [PATCH] i2c: i2c-imx: Use correct function to write to register Michail Georgios Etairidis
2017-06-19 14:46 ` Wolfram Sang
2017-06-20 8:20 ` AW: " Michail Georgios Etairidis
2017-06-20 8:28 ` Uwe Kleine-König
2017-06-20 9:23 ` Wolfram Sang
2017-06-22 8:54 ` Wolfram Sang
2017-06-19 18:54 ` Uwe Kleine-König [this message]
2017-06-20 1:50 ` Andy Duan
-- strict thread matches above, loose matches on Subject: below --
2017-06-08 17:07 Michail Georgios Etairidis
[not found] <681500CE65202E47A192754B01DAB4671B16747DB9@SDE12.beckipc.net>
2017-06-08 16:43 ` Lucas Stach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170619185416.owrkfcbvutbhdrmo@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=B38611@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=lst@pengutronix.de \
--cc=m.etairidis@beck-ipc.com \
--cc=yao.yuan@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).