From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Jean-Christophe PLAGNIOL-VILLARD
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Cc: Marek Roszko
<mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Ludovic Desroches
<ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
mailing list"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v3] i2c:at91: Add device tree property to set clock-frequency
Date: Tue, 11 Mar 2014 12:09:08 +0100 [thread overview]
Message-ID: <20140311110908.GB24766@katana> (raw)
In-Reply-To: <C7EB5260-2285-4572-9D73-15312BB09F65-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
> > Examples :
> > @@ -23,6 +24,7 @@ i2c0: i2c@fff84000 {
> > #address-cells = <1>;
> > #size-cells = <0>;
> > clocks = <&twi0_clk>;
> > + clock-frequency = <400000>;
> >
> The bindings is wrong it’s not the bus frequency but the max frequency
>
> as you describe the bus not the device frequency. And this is this one that limit the bus
It is not wrong, it is since "the beginning" the way i2c bus speeds are
described. It is well known that, in fact, the devices should have a
speed limiting property, yet nobody has sent in patches so far.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-11 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 4:25 [PATCH v3] i2c:at91: Add device tree property to set clock-frequency Marek Roszko
2014-03-11 10:51 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <C7EB5260-2285-4572-9D73-15312BB09F65-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2014-03-11 11:09 ` Wolfram Sang [this message]
[not found] ` <1394511938-28653-1-git-send-email-mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-12 7:26 ` Wolfram Sang
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=20140311110908.GB24766@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
--cc=mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).