devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhangfei <zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	haifeng.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	jchxue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Wei Yan <sledge.yanwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v3 2/3] i2c: hix5hd2: add i2c controller driver
Date: Fri, 03 Oct 2014 21:15:07 +0800	[thread overview]
Message-ID: <542EA15B.70605@linaro.org> (raw)
In-Reply-To: <20141003120926.GF1349@katana>



On 10/03/2014 08:09 PM, Wolfram Sang wrote:
> Hi,
>
> On Tue, Sep 30, 2014 at 08:20:27PM +0800, Zhangfei Gao wrote:
>> From: Wei Yan <sledge.yanwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>>
>> I2C drivers for hix5hd2 soc series, including following chipset
>> Hi3716CV200, Hi3719CV100, Hi3718CV100, Hi3719MV100, Hi3718MV100.
>>
>> Signed-off-by: Wei Yan <sledge.yanwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>
> Looks good to me. You probably want to have a look at this patch
> http://patchwork.ozlabs.org/patch/394648/
>
> an do something similar here, I guess.
>
> BTW what tests have you performed?
>

Thanks Wolfram for the info, will update accordingly.

Currently Wei help do the test via I2C device interface, on a specific 
board with i2c device.
We do the test after the board is up, also no i2c activity during probe.

Thanks

  reply	other threads:[~2014-10-03 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 12:20 [PATCH v3 0/3] i2c: hix5hd2: add i2c controller driver Zhangfei Gao
     [not found] ` <1412079628-6316-1-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-09-30 12:20   ` [PATCH v3 1/3] i2c: hix5hd2: add devicetree documentation Zhangfei Gao
2014-09-30 12:20   ` [PATCH v3 2/3] i2c: hix5hd2: add i2c controller driver Zhangfei Gao
     [not found]     ` <1412079628-6316-3-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-10-03 12:09       ` Wolfram Sang
2014-10-03 13:15         ` zhangfei [this message]
     [not found]           ` <542EA15B.70605-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-10-03 16:48             ` Wolfram Sang
2014-10-04  0:22               ` zhangfei
2014-09-30 12:20   ` [PATCH v3 3/3] ARM: dts: hix5hd2: add i2c node Zhangfei Gao

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=542EA15B.70605@linaro.org \
    --to=zhangfei.gao-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=haifeng.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=jchxue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sledge.yanwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
    --cc=xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.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;
as well as URLs for NNTP newsgroup(s).