linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Trent Piepho <tpiepho@freescale.com>
Subject: Re: i2c-mpc clocking scheme
Date: Mon, 01 Dec 2008 20:40:50 +0100	[thread overview]
Message-ID: <49343DC2.3070601@matrix-vision.de> (raw)
In-Reply-To: <4933FBC6.50100@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

Timur Tabi wrote:
> Trent Piepho wrote:
>
>   
>> Seems like it should keep the clock registers at what u-boot set them too.
>>     
>
> Or we could have U-Boot put the i2c clock frequency into the I2C node, and let
> the driver program the hardware again.  That would keep the ugliness in U-Boot.
>
>   
Wouldn't it be easier to omit frequency re-programming at all ?
Maybe configurable for non U-Boot users ...


MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler  - Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

[-- Attachment #2: Type: text/html, Size: 1015 bytes --]

  reply	other threads:[~2008-12-01 19:39 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 [this message]
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
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=49343DC2.3070601@matrix-vision.de \
    --to=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).