From: Heiko Schocher invitel <heiko.schocher@invitel.hu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] sunxi: i2c: Add DM I2C support for A64/H3/H5
Date: Fri, 28 Apr 2017 08:53:50 +0200 [thread overview]
Message-ID: <5902E6FE.1020507@invitel.hu> (raw)
In-Reply-To: <20170428064422.63bzix5fe7dxdiun@lukather>
Hello Maxime,
Am 28.04.2017 um 08:44 schrieb Maxime Ripard:
> Hello Heiko,
>
> On Fri, Apr 28, 2017 at 05:46:05AM +0200, Heiko Schocher wrote:
>> Hello Jagan,
>>
>> Am 27.04.2017 um 00:03 schrieb Jernej Skrabec:
>>> This series implements DM I2C support, but allows old I2C to be selected
>>> when needed.
>>>
>>> Patch 1 makes sure that sy8106a driver is compiled only during SPL build.
>>>
>>> Patch 2 moves i2c_init_board() function to more convenient place for
>>> follow up patch. It doens't do any functional change.
>>>
>>> Patch 3 introduces DM I2C support for sun6i-a31 compatible I2C
>>> controllers.
>>>
>>> Patch 4 enables DM I2C only for A64/H3/H5. Other platforms would easily
>>> support DM I2C too, but their PMIC drivers needs to be ported to DM in
>>> order not to lose any existing functionality.
>>>
>>> Best regards,
>>> Jernej Skrabec
>>>
>>>
>>> Jernej Skrabec (4):
>>> sunxi: power: Compile sy8106a driver only during SPL build
>>> sunxi: Move function for later convenience
>>> sunxi: i2c: Add support for DM I2C
>>> sunxi: Enable DM_I2C for A64/H3/H5
>>>
>>> arch/arm/mach-sunxi/board.c | 2 +
>>> board/sunxi/Kconfig | 2 +
>>> board/sunxi/board.c | 196 +++++++++++++++++++++--------------------
>>> drivers/i2c/mvtwsi.c | 9 ++
>>> drivers/power/sy8106a.c | 2 +
>>> include/configs/sunxi-common.h | 4 +-
>>> 6 files changed, 120 insertions(+), 95 deletions(-)
>>>
>>
>> Do you want to pick up this patchset?
>>
>> Or should I push it through u-boot-i2c?
>> If so, please add your Ack or Review tag, thanks!
>
> There's a (build) dependency of this work with the current effort to
> bring up HDMI, so I guess it would be easier if we merged it through
> the sunxi tree if it works for you.
Of course. I see this patches in my Patchwork ToDo list. Is it OK
to assign them to jagan?
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2017-04-28 6:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 22:03 [U-Boot] [PATCH 0/4] sunxi: i2c: Add DM I2C support for A64/H3/H5 Jernej Skrabec
2017-04-26 22:03 ` [U-Boot] [PATCH 1/4] sunxi: power: Compile sy8106a driver only during SPL build Jernej Skrabec
2017-04-28 3:42 ` Heiko Schocher
2017-04-26 22:03 ` [U-Boot] [PATCH 2/4] sunxi: Move function for later convenience Jernej Skrabec
2017-04-28 3:43 ` Heiko Schocher
2017-04-26 22:03 ` [U-Boot] [PATCH 3/4] sunxi: i2c: Add support for DM I2C Jernej Skrabec
2017-04-28 3:43 ` Heiko Schocher
2017-04-29 0:28 ` Simon Glass
2017-04-26 22:03 ` [U-Boot] [PATCH 4/4] sunxi: Enable DM_I2C for A64/H3/H5 Jernej Skrabec
2017-04-28 3:44 ` Heiko Schocher
2017-04-27 7:44 ` [U-Boot] [PATCH 0/4] sunxi: i2c: Add DM I2C support " Maxime Ripard
2017-04-28 3:46 ` Heiko Schocher
2017-04-28 6:44 ` Maxime Ripard
2017-04-28 6:53 ` Heiko Schocher invitel [this message]
2017-04-28 7:27 ` Maxime Ripard
2017-04-28 10:04 ` 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=5902E6FE.1020507@invitel.hu \
--to=heiko.schocher@invitel.hu \
--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