From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] i2c: zynq: Add support for the second i2c controller
Date: Thu, 30 Jan 2014 06:27:08 +0100 [thread overview]
Message-ID: <52E9E2AC.5030004@denx.de> (raw)
In-Reply-To: <eec015538ee2c7a66ef62780e8de0321383299f2.1390380363.git.michal.simek@xilinx.com>
Hello Michal,
Am 22.01.2014 09:46, schrieb Michal Simek:
> From: Michael Burr<michael.burr@logicpd.com>
>
> Initialize the second i2c controller.
>
> Signed-off-by: Michael Burr<michael.burr@logicpd.com>
> Signed-off-by: Michal Simek<michal.simek@xilinx.com>
> ---
>
> Changes in v2: None
> Changes in v1:
> - Based on original thread from Michael Burr
> http://lists.denx.de/pipermail/u-boot/2013-October/165017.html
> Heiko did some changes in this mainline patch
> "i2c, zynq: convert zynq i2c driver to new multibus/multiadapter framework"
> (sha1: 0bdffe71fddeaa46768a39305797e4512dee0f15)
> - MS rebase on latest&greatest
>
> drivers/i2c/zynq_i2c.c | 44 ++++++++++++++++++++++++++-----------------
> include/configs/zynq-common.h | 6 +++---
> 2 files changed, 30 insertions(+), 20 deletions(-)
Applied to u-boot-i2c.git, thanks!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2014-01-30 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 8:46 [U-Boot] [PATCH v2 1/2] i2c: zynq: Support for 0-length register address Michal Simek
2014-01-22 8:46 ` [U-Boot] [PATCH v2 2/2] i2c: zynq: Add support for the second i2c controller Michal Simek
2014-01-30 5:27 ` Heiko Schocher [this message]
2014-01-30 5:26 ` [U-Boot] [PATCH v2 1/2] i2c: zynq: Support for 0-length register address 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=52E9E2AC.5030004@denx.de \
--to=hs@denx.de \
--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