From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Tin Huynh <tnhuynh@apm.com>, Richard Purdie <rpurdie@rpsys.net>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Loc Ho <lho@apm.com>, Phong Vo <pvo@apm.com>,
Thang Nguyen <tqnguyen@apm.com>,
patches@apm.com
Subject: Re: [PATCH V1] leds: pca955x: Correct I2C Functionality
Date: Mon, 22 May 2017 21:02:29 +0200 [thread overview]
Message-ID: <860beb3d-67e5-2e01-c430-897759633ec9@gmail.com> (raw)
In-Reply-To: <1495444760-7626-1-git-send-email-tnhuynh@apm.com>
Hi Tin,
On 05/22/2017 11:19 AM, Tin Huynh wrote:
> The driver checks an incorrect flag of functionality of adapter.
> When a driver requires i2c_smbus_read_byte_data and
> i2c_smbus_write_byte_data, it should check I2C_FUNC_SMBUS_BYTE_DATA
> instead I2C_FUNC_I2C.
> This patch fixes the problem.
>
> Signed-off-by: Tin Huynh <tnhuynh@apm.com>
> ---
> drivers/leds/leds-pca955x.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/leds/leds-pca955x.c b/drivers/leds/leds-pca955x.c
> index 78a7ce8..9a87311 100644
> --- a/drivers/leds/leds-pca955x.c
> +++ b/drivers/leds/leds-pca955x.c
> @@ -285,7 +285,7 @@ static int pca955x_probe(struct i2c_client *client,
> "slave address 0x%02x\n",
> client->name, chip->bits, client->addr);
>
> - if (!i2c_check_functionality(adapter, I2C_FUNC_I2C))
> + if (!i2c_check_functionality(adapter, I2C_FUNC_SMBUS_BYTE_DATA))
> return -EIO;
>
> if (pdata) {
>
Applied to the fixes-for-4.12rc3 branch of linux-leds.git, thanks.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2017-05-22 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:19 Tin Huynh
2017-05-22 19:02 ` Jacek Anaszewski [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=860beb3d-67e5-2e01-c430-897759633ec9@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=lho@apm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=patches@apm.com \
--cc=pavel@ucw.cz \
--cc=pvo@apm.com \
--cc=rpurdie@rpsys.net \
--cc=tnhuynh@apm.com \
--cc=tqnguyen@apm.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
all inboxes | Powered by JetHome®