linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Jason McMullan <jason.mcmullan@timesys.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Updated: CPM2 I2C (SDMA and BitBang)
Date: Sun, 27 Mar 2005 20:11:19 -0800	[thread overview]
Message-ID: <20050328041119.GA30818@gate.ebshome.net> (raw)
In-Reply-To: <1111525951.2987.76.camel@ad.doubleclick.net>

On Tue, Mar 22, 2005 at 04:12:30PM -0500, Jason McMullan wrote:
> #### Auto-generated patch ####
> Date:        Tue, 22 Mar 2005 15:59:01 -0500
> Maintainer:  Jason McMullan <jmcmullan@timesys.com>
> Summary:     CPM/CPM2 I2C driver for Freescale SoC devices
> Description: CPM/CPM2 I2C driver for Freescale SoC devices
> Depends:
> 	
> ###############################
> 
> Index of changes:
> 
>  drivers/i2c/algos/Kconfig              |    4 
>  drivers/i2c/algos/Makefile             |    1 
>  drivers/i2c/busses/Kconfig             |   25 +
>  drivers/i2c/busses/Makefile            |    1 
>  include/linux/i2c-id.h                 |    4 
>  linux/drivers/i2c/algos/i2c-algo-cpm.c |  477 +++++++++++++++++++++++++++++++++
>  linux/drivers/i2c/busses/i2c-cpm.c     |  219 +++++++++++++++
>  linux/include/linux/i2c-algo-cpm.h     |   64 ++++

[snip]

Jason, another thought. Do we really need all this mess with separate 
algo and bus drivers?

Could you make just a bus driver like we have for 4xx, Keywest and 
85xx/52xx/MPC107? It's much cleaner and less confusing IMHO.

--
Eugene

  reply	other threads:[~2005-03-28  4:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 21:12 [PATCH] Updated: CPM2 I2C (SDMA and BitBang) Jason McMullan
2005-03-28  4:11 ` Eugene Surovegin [this message]
2005-03-28 14:17   ` Jason McMullan

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=20050328041119.GA30818@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=jason.mcmullan@timesys.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).