From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 0/2] Add cdns-i2c driver as drop in for zynq-i2c
Date: Wed, 6 Jan 2016 08:53:12 +0100 [thread overview]
Message-ID: <568CC7E8.5090003@xilinx.com> (raw)
In-Reply-To: <CAAtXAHc6Rf2NWrT2Xaz34S+CKLQ0s=AVoMd9CCRTc9kq-Qc9aQ@mail.gmail.com>
On 5.1.2016 18:30, Moritz Fischer wrote:
> Hi Michal,
>
> On Tue, Jan 5, 2016 at 7:44 AM, Michal Simek <michal.simek@xilinx.com> wrote:
>
>> I have looked at these patches and I don't know why there is 100k
>> limitation in cdns_i2c_set_bus_speed. DTS is using 400k in Linux without
>> any problem.
>
> Well I could statically calculate the values for 400K, too but anyway that works
> only if your CPU_CLK_1X is 111MHz. Is there a way to figure out the CPU_CLK_1X
> frequency?
Check the clock driver.
>> Unfortunately I found that i2c muxes like pca9548 are not supported yet
>> but I have create sort of skeleton for that but it looks like that there
>> is no standard binding where i2c-parent is required. Also every muxes
>> bus needs to have correct label and alias.
>
> Yeah, I realized that last night when I started playing around with
> it. I was trying
> to pull in the linux one but didn't get around to finish that yet.
It is simple to create that mux drivers but I am scared about that need
for aliases and also i2c-parent has to go out of mux class too.
I see that it is used in the mainline kernel but it has be changed.
>> Also I have found that there is eeprom dependency which needs to be
>> resolved to be able to use this driver instead of old one.
>
> Yeah I realized that. Do any of the zynq boards actually use CMD_EEPROM?
We have a code for zc702 to save internal variables to EEPROM. zc706
should have that memory too.
Thanks,
Michal
next prev parent reply other threads:[~2016-01-06 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 17:47 [U-Boot] [RFC 0/2] Add cdns-i2c driver as drop in for zynq-i2c Moritz Fischer
2015-12-28 17:47 ` [U-Boot] [RFC 1/2] i2c: Describe Cadence I2C devicetree bindings Moritz Fischer
2016-01-04 7:09 ` Heiko Schocher
2015-12-28 17:47 ` [U-Boot] [RFC 2/2] dm: i2c: Add driver for Cadence I2C IP Moritz Fischer
2016-01-04 7:15 ` Heiko Schocher
2016-04-11 12:50 ` Michal Simek
2016-04-12 7:45 ` Heiko Schocher
2016-04-12 7:59 ` Michal Simek
2015-12-28 18:35 ` [U-Boot] [RFC 0/2] Add cdns-i2c driver as drop in for zynq-i2c Michal Simek
2015-12-28 19:15 ` Moritz Fischer
2016-01-05 15:44 ` Michal Simek
2016-01-05 17:30 ` Moritz Fischer
2016-01-06 7:53 ` Michal Simek [this message]
2016-01-07 5:18 ` Moritz Fischer
2016-01-07 8:13 ` Michal Simek
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=568CC7E8.5090003@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.