linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Armin Kuster <akuster@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Further OCP cleanups
Date: Mon, 20 May 2002 11:36:59 +1000	[thread overview]
Message-ID: <20020520013659.GR4745@zax> (raw)
In-Reply-To: <3CE579E1.1090504@mvista.com>


On Fri, May 17, 2002 at 02:45:05PM -0700, Armin Kuster wrote:
> David Gibson wrote:
> >The patch below follows up on paulus' cleanups of the OCP EMAC driver
> >with further cleanups in the OCP layer and its drivers.  It does
> >several things:
> >	- Renames the ocpdev field of struct ocp_driver to private,
> >which is more descriptive of its actual function.
> >	- removes a redundant INIT_LIST_HEAD from ocp_register
> >	- moves the registration of the miscdev for the GPIO driver
> >into the driver itself, from ocp.c
> >	- removes the irq_resource field of the ocp_enet_private
> >structure, since it was essentially unused.
> >	- with the help of those last two remove the ugly switch
> >statements from ocp_register() and ocp_unregister()
> >	- removed the procdir field from ocp_driver structure, since
> >it always had the same value
> >	- remove the fops field from the ocp_driver structure, since
> >it was only used by the GPIO driver and then always held the same
> >value
> >	- cleanup of the MAL DCR handling code.  No more mal.sh,
> >autogenerated ibm_ocp_mal.c or MBASE[].  Instead we use a magic macro
> >to generate a switch across the MAL base address.  More to come which
> >will cause this to be completely optimised away on machines with only
> >one MAL (the majority)
> >	- Move the IIC_DEV macro into the .c files which use it, since
> >it clearly belongs to the I2C code itself, rather than to the OCP
> >layer.  More to come which will eliminate this macro entirely, as
> >EMAC_DEV was removed by paulus' patch
> >	- Update ibm_ocp_debug.c to work with paulus' changes, also
> >cleanup some ugliness
> >	- Remove the 'priv_index', 'devfs_handle' and 'active' fields
> >from struct ocp_driver, since they appear to be unused.
> >
> >If you have no objections I will commit this to linuxppc_2_4_devel.
>
> David,
>
>  The IIC_DEV change is ok and the _debug.c changes are fine but  I
> would like to hold off on the rest.  I am not satisfied with the tx/rx
> channel mal case/switch stuff in the *_enet.c and the ibmnp405h.c was
> missed

Um... I don't see what connection that has with my patch.  It has only
a tenous relationship to the MAL changes and is unrelated to
everything else.

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-05-20  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020517052718.GH4745@zax>
2002-05-17 21:45 ` Further OCP cleanups Armin Kuster
2002-05-20  1:36   ` David Gibson [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=20020520013659.GR4745@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=akuster@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.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).