From: Bo Shen <voice.shen@atmel.com>
To: "Raphaël Poggi" <poggi.raph@gmail.com>, barebox@lists.infradead.org
Subject: Re: [PATCH] i2c: at91: add at91sam9x5 config
Date: Mon, 4 Aug 2014 15:40:40 +0800 [thread overview]
Message-ID: <53DF38F8.5050807@atmel.com> (raw)
In-Reply-To: <53DF3790.1050804@atmel.com>
Hi Raphaël Poggi,
On 08/04/2014 03:34 PM, Bo Shen wrote:
> Hi Raphaël Poggi,
> Actually, this is a build fix.
>
> On 08/01/2014 09:26 PM, Raphaël Poggi wrote:
>> Signed-off-by: Raphaël Poggi <poggi.raph@gmail.com>
>
> Acked-by: Bo Shen <voice.shen@atmel.com>
Sorry, can you squash this patch into "[PATCH 1/2] i2c: at91: add
support of device tree"
>> ---
>> drivers/i2c/busses/i2c-at91.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/i2c/busses/i2c-at91.c
>> b/drivers/i2c/busses/i2c-at91.c
>> index 399f6a9..4aa4e4e 100644
>> --- a/drivers/i2c/busses/i2c-at91.c
>> +++ b/drivers/i2c/busses/i2c-at91.c
>> @@ -346,6 +346,12 @@ static struct at91_twi_pdata at91sam9g10_config = {
>> .has_unre_flag = false,
>> };
>>
>> +static struct at91_twi_pdata at91sam9x5_config = {
>> + .clk_max_div = 7,
>> + .clk_offset = 4,
>> + .has_unre_flag = false,
>> +};
>> +
>> static struct platform_device_id at91_twi_devtypes[] = {
>> {
>> .name = "i2c-at91rm9200",
>>
>
> Best Regards,
> Bo Shen
Best Regards,
Bo Shen
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-08-04 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 13:26 Raphaël Poggi
2014-08-04 7:34 ` Bo Shen
2014-08-04 7:40 ` Bo Shen [this message]
2014-09-24 12:57 [PATCH] i2c: at91: fix coding style issue Raphaël Poggi
2014-09-24 12:57 ` [PATCH] i2c: at91: add at91sam9x5 config Raphaël Poggi
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=53DF38F8.5050807@atmel.com \
--to=voice.shen@atmel.com \
--cc=barebox@lists.infradead.org \
--cc=poggi.raph@gmail.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