public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Daniel Silverstone <dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org,
	Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [PATCH] Bugfix for i2c-s3c2410
Date: Tue, 17 Feb 2009 13:10:01 +0000	[thread overview]
Message-ID: <20090217131001.GC19758@fluff.org.uk> (raw)
In-Reply-To: <1234446401.9457.25.camel@petitemort>

On Thu, Feb 12, 2009 at 01:46:41PM +0000, Daniel Silverstone wrote:
> I2C: Rework i2c-s3c2410 frequency calculator to be much simpler.

I think you wanted this as the subject of the patch.
 
> The platform data for the i2c-s3c2410 driver used to allow a min,
> max and desired frequency for the I2C bus. This patch reduces it
> to simply a desired frequency ceiling and corrects all the uses
> of the platform data appropriately.
> 
> This means, for example, that on a system with a 66MHz fclk, a
> request for 100KHz will achieve 65KHz which is safe and
> acceptable, rather than 378KHz which it would have achieved
> without this change.
> 
> Signed-off-by: Simtec Linux Team <linux-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>
> Signed-off-by: Daniel Silverstone <dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org>

The rest of the patch is ok.

-- 
Ben (ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

  parent reply	other threads:[~2009-02-17 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 13:46 [PATCH] Bugfix for i2c-s3c2410 Daniel Silverstone
2009-02-12 13:54 ` Daniel Silverstone
2009-02-17 13:10 ` Ben Dooks [this message]
2009-03-13 13:53 ` Daniel Silverstone

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=20090217131001.GC19758@fluff.org.uk \
    --to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
    --cc=dsilvers-Y5A6D6n0/KfQXOPxS62xeg@public.gmane.org \
    --cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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