From: Timur Tabi <timur@freescale.com>
To: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
Cc: linuxppc-dev@ozlabs.org, Trent Piepho <tpiepho@freescale.com>
Subject: Re: i2c-mpc clocking scheme
Date: Mon, 01 Dec 2008 13:48:06 -0600 [thread overview]
Message-ID: <49343F76.3060802@freescale.com> (raw)
In-Reply-To: <49343DC2.3070601@matrix-vision.de>
André Schwarz wrote:
> Wouldn't it be easier to omit frequency re-programming at all ?
> Maybe configurable for non U-Boot users ...
Well, the real problem is that Linux is ignoring what the boot loader has done.
This is bad, regardless as to which boot loader you're using.
The question is, do we give Linux the capability to program the I2C bus speed,
or is this something that the boot loader should do? Unfortunately, the current
Linux code means that this issue is not properly architected.
You mentioned people who don't use U-Boot. Do they use some other boot loader?
Or no boot loader at all? Do other boot loaders program the I2C bus speed?
The reason I ask is that I want to know whether it's okay for Linux to ignore
the FDR and DFSRR registers.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-12-01 19:48 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 [this message]
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
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=49343F76.3060802@freescale.com \
--to=timur@freescale.com \
--cc=Andre.Schwarz@matrix-vision.de \
--cc=linuxppc-dev@ozlabs.org \
--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).