From: zhangfei.gao@linaro.org (zhangfei)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] i2c-designware: support no DW_IC_COMP_TYPE platform
Date: Sun, 09 Jun 2013 16:47:28 +0800 [thread overview]
Message-ID: <51B44120.5060304@linaro.org> (raw)
In-Reply-To: <20130609030600.GA4312@tarshish>
On 13-06-09 11:06 AM, Baruch Siach wrote:
> Hi Zhangfei Gao,
>
> On Sun, Jun 09, 2013 at 10:36:41AM +0800, Zhangfei Gao wrote:
>> Check accessor_flags before reading DW_IC_COMP_TYPE
>> Give chance to platform no such register
>>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> ---
>> drivers/i2c/busses/i2c-designware-core.c | 24 +++++++++++++-----------
>> drivers/i2c/busses/i2c-designware-core.h | 1 +
>> 2 files changed, 14 insertions(+), 11 deletions(-)
>
> [...]
>
>> diff --git a/drivers/i2c/busses/i2c-designware-core.h
>> b/drivers/i2c/busses/i2c-designware-core.h
>> index e761ad1..b38b54e 100644
>> --- a/drivers/i2c/busses/i2c-designware-core.h
>> +++ b/drivers/i2c/busses/i2c-designware-core.h
>> @@ -94,6 +94,7 @@ struct dw_i2c_dev {
>>
>> #define ACCESS_SWAP 0x00000001
>> #define ACCESS_16BIT 0x00000002
>> +#define ACCESS_32BIT 0x00000004
>
> This belongs to the next patch, not to this one.
>
> baruch
>
Thanks baruch, make sense.
next prev parent reply other threads:[~2013-06-09 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 2:36 [PATCH 0/2] support i2c-designware-hs Zhangfei Gao
2013-06-09 2:36 ` [PATCH 1/2] i2c-designware: support no DW_IC_COMP_TYPE platform Zhangfei Gao
2013-06-09 3:06 ` Baruch Siach
2013-06-09 8:47 ` zhangfei [this message]
2013-06-09 2:36 ` [PATCH 2/2] i2c: designware: Add i2c-designware-hs Zhangfei Gao
2013-06-09 3:23 ` Baruch Siach
2013-06-09 3:23 ` Baruch Siach
2013-06-09 8:59 ` zhangfei gao
2013-06-09 8:59 ` zhangfei gao
2013-06-09 9:50 ` Baruch Siach
2013-06-09 9:50 ` Baruch Siach
2013-06-09 16:03 ` zhangfei
2013-06-09 16:03 ` zhangfei
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=51B44120.5060304@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 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.