From: Tushar Behera <tushar.behera@linaro.org>
To: linux-i2c@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: ben-linux@fluff.org, kgene.kim@samsung.com,
linaro-dev@lists.linaro.org, patches@linaro.org,
thomas.abraham@linaro.org
Subject: Re: [PATCH] i2c-s3c2410: Fix return code of s3c24xx_i2c_parse_dt_gpio
Date: Mon, 19 Dec 2011 09:35:44 +0530 [thread overview]
Message-ID: <4EEEB818.406@linaro.org> (raw)
In-Reply-To: <1323425035-11298-1-git-send-email-tushar.behera@linaro.org>
Ping
On 12/09/2011 03:33 PM, Tushar Behera wrote:
> s3c24xx_i2c_parse_dt_gpio is called when cfg_gpio is not defined
> in the platform data of the i2c device. When DT is not enabled,
> the above function always returns -EINVAL. Since there can be
> some i2c devices which don't need to configure any gpio lines,
> the probe of such devices would fail here. Changing the default
> return value to success would fix this issue.
>
> Signed-off-by: Tushar Behera<tushar.behera@linaro.org>
> ---
> This patch is rebased on Kukjin's for-next branch.
> d3d936c "Merge branch 'samsung-fixes-2' into for-next"
>
> drivers/i2c/busses/i2c-s3c2410.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
> index 2754cef..b5caa42 100644
> --- a/drivers/i2c/busses/i2c-s3c2410.c
> +++ b/drivers/i2c/busses/i2c-s3c2410.c
> @@ -786,7 +786,7 @@ static void s3c24xx_i2c_dt_gpio_free(struct s3c24xx_i2c *i2c)
> #else
> static int s3c24xx_i2c_parse_dt_gpio(struct s3c24xx_i2c *i2c)
> {
> - return -EINVAL;
> + return 0;
> }
>
> static void s3c24xx_i2c_dt_gpio_free(struct s3c24xx_i2c *i2c)
--
Tushar Behera
prev parent reply other threads:[~2011-12-19 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 10:03 [PATCH] i2c-s3c2410: Fix return code of s3c24xx_i2c_parse_dt_gpio Tushar Behera
2011-12-19 4:05 ` Tushar Behera [this message]
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=4EEEB818.406@linaro.org \
--to=tushar.behera@linaro.org \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=thomas.abraham@linaro.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