public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: i2c@lm-sensors.org, linux-sh@vger.kernel.org,
	Paul Mundt <lethal@linux-sh.org>, Ben Dooks <ben-linux@fluff.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] i2c: SuperH Mobile I2C Bus Controller V5
Date: Sat, 05 Apr 2008 08:50:33 +0000	[thread overview]
Message-ID: <20080405105033.3687c785@hyperion.delvare> (raw)
In-Reply-To: <20080402025950.1026.44461.sendpatchset@rx1.opensource.se>

Hi Magnus,

On Wed, 02 Apr 2008 11:59:50 +0900, Magnus Damm wrote:
> This is V5 of the SuperH Mobile I2C Controller Driver. A simple Master
> only driver for the I2C block included in processors such as sh7343,
> sh7722 and sh7723. Tested on a sh7722 MigoR using a rs5c732b rtc.
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> ---
> 
>  Changes since V4:
>   - Use sh_mobile_i2c_op enum
>   - Remove fast_mode and rx_ack_high code
>   - Use variable name retry_count instead of k
>   - Encoding fixes
>   - Use clk_enable() and clk_disable()
>   - Remove deactivate_ch() call from setup_channel()
>   - Use dev_err() if i2c_add_numbered_adapter() fails
>   - MODULE_LICENSE("GPL v2")
>   - Comment fix, cleaned up header
>  Changes since V3:
>   - Added SUPERH Kconfig dependency
>   - Use spin_lock_irqsave() and spin_unlock_irqrestore()
>   - Use IRQF_DISABLED
>   - Checkpatch fixes
>  Changes since V2:
>   - dev_xxx() use
>   - Kill off superfluous ioarea resource
>   - Add SMBus emulation
>  Changes since V1:
>   - Use clk_get()/clk_put()/clk_get_rate() to get peripheral clock rate.
>   - Use pdev->dev.bus_id instead of dev->name
> 
>  Verified with the rtc-rs5c372 SMBus conversion patches currently in -mm.
> 
>  drivers/i2c/busses/Kconfig         |   10 
>  drivers/i2c/busses/Makefile        |    1 
>  drivers/i2c/busses/i2c-sh_mobile.c |  500 ++++++++++++++++++++++++++++++++++++
>  3 files changed, 511 insertions(+)

Patch added to my i2c tree and queued up for merge in 2.6.26-rc1.
Thanks to everyone who reviewed the previous versions of the driver.

-- 
Jean Delvare

      reply	other threads:[~2008-04-05  8:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 14:18 [PATCH] i2c: SuperH Mobile I2C Bus Controller Magnus Damm
2008-03-21  6:23 ` Paul Mundt
2008-03-21  8:14   ` Magnus Damm
2008-03-21 12:07 ` [PATCH] i2c: SuperH Mobile I2C Bus Controller V2 Magnus Damm
2008-03-25 10:55 ` [PATCH] i2c: SuperH Mobile I2C Bus Controller V3 Paul Mundt
2008-03-26 19:56   ` Andrew Morton
2008-03-27 22:07   ` Andrew Morton
2008-03-28  9:35 ` [PATCH] i2c: SuperH Mobile I2C Bus Controller V4 Magnus Damm
2008-03-29 17:57   ` [i2c] " Ben Dooks
     [not found]     ` <20080329175732.GA9638-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-03-29 19:57       ` Jean Delvare
2008-03-31 22:36     ` [i2c] " Andrew Morton
2008-04-02  1:20     ` Magnus Damm
2008-04-02  2:59 ` [PATCH] i2c: SuperH Mobile I2C Bus Controller V5 Magnus Damm
2008-04-05  8:50   ` Jean Delvare [this message]

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=20080405105033.3687c785@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=ben-linux@fluff.org \
    --cc=i2c@lm-sensors.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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