linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Trent Piepho <tpiepho@freescale.com>
Cc: "André Schwarz" <Andre.Schwarz@matrix-vision.de>,
	"Timur Tabi" <timur@freescale.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: i2c-mpc clocking scheme
Date: Mon, 01 Dec 2008 16:26:31 -0600	[thread overview]
Message-ID: <49346497.8050701@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812011347450.10176@t2.domain.actdsltmp>

Trent Piepho wrote:
> U-boot could pass in "bus-frequency" to let software know the speed of the
> I2C bus from Linux.  Seems like a standard property for bus nodes.

clock-frequency is standard, though it should probably be the input 
frequency rather than the bus frequency, in case the OS really does want 
to change it (maybe making the bus run faster when accessing faster 
devices).

> There could be a "current-speed" property that tells linux to keep the
> registers the same,

That would be a bit different from the way it's used in serial nodes, 
where current-speed is simply a description of the baud rate that 
corresponds to the current divider setting.  I'm not sure that it makes 
as much sense for i2c, as you don't have the shared state on the other 
end that depends on maintaining the exact same speed.

When does the guest really care what the specific i2c bus frequency is, 
if it's not going to change it?

-Scott

  reply	other threads:[~2008-12-01 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 15:00 i2c-mpc clocking scheme Andre Schwarz
2008-11-27 15:24 ` Timur Tabi
2008-11-27 15:43   ` Andre Schwarz
2008-11-28 20:59     ` Trent Piepho
2008-12-01 14:59       ` Timur Tabi
2008-12-01 19:40         ` André Schwarz
2008-12-01 19:48           ` Timur Tabi
2008-12-01 22:07           ` Trent Piepho
2008-12-01 22:26             ` Scott Wood [this message]
2008-12-01 22:57               ` Trent Piepho
2008-12-01 23:00                 ` Timur Tabi
2008-12-01 23:07                 ` Scott Wood
2008-11-27 15:49   ` Luotao Fu

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=49346497.8050701@freescale.com \
    --to=scottwood@freescale.com \
    --cc=Andre.Schwarz@matrix-vision.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    --cc=tpiepho@freescale.com \
    /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).