public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Marek Szyprowski'" <m.szyprowski@samsung.com>,
	<linux-samsung-soc@vger.kernel.org>, <linux-i2c@vger.kernel.org>
Cc: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	"'Alim Akhtar'" <alim.akhtar@samsung.com>,
	"'Andi Shyti'" <andi.shyti@kernel.org>,
	"'Wolfram Sang'" <wsa@kernel.org>
Subject: RE: [PATCH v2 2/3] i2c: s3c24xx: fix transferring more than one message in polling mode
Date: Fri, 27 Oct 2023 19:55:01 +0900	[thread overview]
Message-ID: <000801da08c4$08990830$19cb1890$@samsung.com> (raw)
In-Reply-To: <20231025121725.46028-3-m.szyprowski@samsung.com>

> -----Original Message-----
> From: Marek Szyprowski <m.szyprowski@samsung.com>
> Sent: Wednesday, October 25, 2023 9:17 PM
> To: linux-samsung-soc@vger.kernel.org; linux-i2c@vger.kernel.org
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>; Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org>; Alim Akhtar <alim.akhtar@samsung.com>;
> Andi Shyti <andi.shyti@kernel.org>; Wolfram Sang <wsa@kernel.org>
> Subject: [PATCH v2 2/3] i2c: s3c24xx: fix transferring more than one
> message in polling mode
> 
> To properly handle ACK on the bus when transferring more than one
> message in polling mode, move the polling handling loop from
> s3c24xx_i2c_message_start() to s3c24xx_i2c_doxfer(). This way
> i2c_s3c_irq_nextbyte() is always executed till the end, properly
> acknowledging the IRQ bits and no recursive calls to
> i2c_s3c_irq_nextbyte() are made.
> 
> While touching this, also fix finishing transfers in polling mode by
> using common code path and always waiting for the bus to become idle
> and disabled.
> 
> Fixes: 117053f77a5a ("i2c: s3c2410: Add polling mode support")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>

Reviewed-by: Chanho Park <chanho61.park@samsung.com>

> ---
>  drivers/i2c/busses/i2c-s3c2410.c | 25 ++++++++++---------------
>  1 file changed, 10 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-
> s3c2410.c
> index f9dcb1112a61..8da85cb42980 100644
> --- a/drivers/i2c/busses/i2c-s3c2410.c
> +++ b/drivers/i2c/busses/i2c-s3c2410.c
> @@ -275,16 +275,6 @@ static void s3c24xx_i2c_message_start(struct
> s3c24xx_i2c *i2c,
> 
>  	stat |= S3C2410_IICSTAT_START;
>  	writel(stat, i2c->regs + S3C2410_IICSTAT);
> -
> -	if (i2c->quirks & QUIRK_POLL) {
> -		while ((i2c->msg_num != 0) && is_ack(i2c)) {
> -			i2c_s3c_irq_nextbyte(i2c, stat);
> -			stat = readl(i2c->regs + S3C2410_IICSTAT);
> -
> -			if (stat & S3C2410_IICSTAT_ARBITR)
> -				dev_err(i2c->dev, "deal with arbitration
> loss\n");
> -		}
> -	}
>  }
> 
>  static inline void s3c24xx_i2c_stop(struct s3c24xx_i2c *i2c, int ret)
> @@ -691,7 +681,7 @@ static void s3c24xx_i2c_wait_idle(struct s3c24xx_i2c
> *i2c)
>  static int s3c24xx_i2c_doxfer(struct s3c24xx_i2c *i2c,
>  			      struct i2c_msg *msgs, int num)
>  {
> -	unsigned long timeout;
> +	unsigned long timeout = 0;
>  	int ret;
> 
>  	ret = s3c24xx_i2c_set_master(i2c);
> @@ -711,16 +701,21 @@ static int s3c24xx_i2c_doxfer(struct s3c24xx_i2c
> *i2c,
>  	s3c24xx_i2c_message_start(i2c, msgs);
> 
>  	if (i2c->quirks & QUIRK_POLL) {
> -		ret = i2c->msg_idx;
> +		while ((i2c->msg_num != 0) && is_ack(i2c)) {
> +			unsigned long stat = readl(i2c->regs +
> S3C2410_IICSTAT);
> 
> -		if (ret != num)
> -			dev_dbg(i2c->dev, "incomplete xfer (%d)\n", ret);
> +			i2c_s3c_irq_nextbyte(i2c, stat);
> 
> -		goto out;
> +			stat = readl(i2c->regs + S3C2410_IICSTAT);
> +			if (stat & S3C2410_IICSTAT_ARBITR)
> +				dev_err(i2c->dev, "deal with arbitration
> loss\n");
> +		}
> +		goto skip_waiting;
>  	}
> 
>  	timeout = wait_event_timeout(i2c->wait, i2c->msg_num == 0, HZ * 5);
> 
> + skip_waiting:
>  	ret = i2c->msg_idx;
> 
>  	/*
> --
> 2.34.1



  reply	other threads:[~2023-10-27 10:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231025121735eucas1p22b65a2c0bc6d30342c4935e3903823a1@eucas1p2.samsung.com>
2023-10-25 12:17 ` [PATCH v2 0/3] Add atomic transfers to s3c24xx i2c driver Marek Szyprowski
2023-10-25 12:17   ` [PATCH v2 1/3] i2c: s3c24xx: fix read transfers in polling mode Marek Szyprowski
2023-10-27 10:54     ` Chanho Park
     [not found]     ` <20231027133950.kntkq6ddgifaor76@zenone.zhora.eu>
2023-10-31 14:00       ` Marek Szyprowski
     [not found]       ` <3484d2c1-942b-4145-801f-8b8bda7dd9ec@samsung.com>
2023-11-02  0:49         ` Andi Shyti
2023-11-02 11:07           ` Marek Szyprowski
2023-11-02  1:31     ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-11-02 11:23       ` Marek Szyprowski
     [not found]       ` <ace37058-1bcb-4fb4-8ffe-628f5e9249c0@samsung.com>
2023-11-02 23:35         ` Andi Shyti
2023-10-25 12:17   ` [PATCH v2 2/3] i2c: s3c24xx: fix transferring more than one message " Marek Szyprowski
2023-10-27 10:55     ` Chanho Park [this message]
2023-10-25 12:17   ` [PATCH v2 3/3] i2c: s3c24xx: add support for atomic transfers Marek Szyprowski
2023-10-27 10:54     ` Chanho Park

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='000801da08c4$08990830$19cb1890$@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andi.shyti@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=wsa@kernel.org \
    /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