From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: Instantiate I2C controllers when selected
Date: Wed, 28 Oct 2015 08:08:19 +0100 [thread overview]
Message-ID: <56307463.7070404@xilinx.com> (raw)
In-Reply-To: <56306393.3010809@denx.de>
Hi Heiko,
On 10/28/2015 06:56 AM, Heiko Schocher wrote:
> Hello Michal,
>
> Am 27.10.2015 um 16:02 schrieb Michal Simek:
>> Do not enable both I2C controllers by default. Enable them only when
>> they are selected.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> drivers/i2c/zynq_i2c.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> Thanks!
>
> I will accept this patch, but it is a fix for the old style
> I2C driver. I would prefer a patch, which converts this driver
> to DM ;-)
We will do it soon.
>
> What do you mean with "enabled"? The old style i2c driver,
> does not initialize (call zynq_i2c_init()) the i2c driver, until
> it is used ... nevertheless, you save some bytes, which is always
> good.
All zynq devices have 2 I2C core inside but not all of them are
connected to the board from chip. I don't know why but both of them were
enabled by default. Configuration should be done based on real
connection on the board. It means only certain I2C controller (or both)
should be enabled via board file.
This will be solved by moving driver to DM.
> Reviewed-by: Heiko Schocher <hs@denx.de>
Are you going to queue this? Or do you want me to take it via arm zynq repo?
Thanks,
Michal
next prev parent reply other threads:[~2015-10-28 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:02 [U-Boot] [PATCH] i2c: Instantiate I2C controllers when selected Michal Simek
2015-10-28 5:56 ` Heiko Schocher
2015-10-28 7:08 ` Michal Simek [this message]
2015-10-28 8:55 ` 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=56307463.7070404@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