From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] dm: i2c: Add driver for Cadence I2C IP
Date: Wed, 13 Apr 2016 08:01:00 +0200 [thread overview]
Message-ID: <570DE09C.8070101@xilinx.com> (raw)
In-Reply-To: <570DDCDA.4070206@denx.de>
On 13.4.2016 07:44, Heiko Schocher wrote:
> Hello Michal,
>
> Am 11.04.2016 um 14:55 schrieb Michal Simek:
>> From: Moritz Fischer <moritz.fischer@ettus.com>
>>
>> This is a possible drop in replacement for drivers/i2c/zynq-i2c.c
>>
>> Since this is cadence IP it has been renamed to cdns-i2c,
>> to make sense with the compatible string.
>>
>> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Changes in v2:
>> - Use dev_get_addr for reading address.
>>
>> This driver will be used by ZynqMP. Zynq will use zynq-i2c driver
>> till eeprom interface is fixed but this driver can be also enabled for
>> Zynq targets.
>>
>> ---
>> drivers/i2c/Kconfig | 7 ++
>> drivers/i2c/Makefile | 1 +
>> drivers/i2c/i2c-cdns.c | 335
>> +++++++++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 343 insertions(+)
>> create mode 100644 drivers/i2c/i2c-cdns.c
>
> Reviewed-by: Heiko Schocher <hs@denx.de>
Do you want me to take this via my xilinx tree? Or are you going to take
it via i2c tree?
Thanks,
Michal
next prev parent reply other threads:[~2016-04-13 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 12:55 [U-Boot] [PATCH v2 1/2] i2c: Describe Cadence I2C devicetree bindings Michal Simek
2016-04-11 12:55 ` [U-Boot] [PATCH v2 2/2] dm: i2c: Add driver for Cadence I2C IP Michal Simek
2016-04-13 5:44 ` Heiko Schocher
2016-04-13 6:01 ` Michal Simek [this message]
2016-04-13 6:12 ` Heiko Schocher
2016-04-13 6:24 ` Michal Simek
2016-04-13 5:44 ` [U-Boot] [PATCH v2 1/2] i2c: Describe Cadence I2C devicetree bindings Heiko Schocher
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=570DE09C.8070101@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/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