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

Trent Piepho wrote:

> For a bus device like an i2c controller, you really have two clocks.  The
> input clock the controller runs from and the speed it runs the bus at.  One
> could say that one clock is for the device node and the other clock is for
> the device's sub-nodes.

We could add a property to each I2C device nodes that lists the maximum speed
that this supports.  Then the I2C driver could find the smallest of these
speeds, and program the I2C controller for that speed.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-12-01 23:01 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
2008-12-01 22:57               ` Trent Piepho
2008-12-01 23:00                 ` Timur Tabi [this message]
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=49346C9E.4090906@freescale.com \
    --to=timur@freescale.com \
    --cc=Andre.Schwarz@matrix-vision.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@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).