linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Li Yang" <LeoLi@freescale.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 0/9] Add support for QE and 8360EMDS board -v3
Date: Fri, 29 Sep 2006 22:54:46 +0800	[thread overview]
Message-ID: <a0bc9bf80609290754s1ba72951m9825980b05025bef@mail.gmail.com> (raw)
In-Reply-To: <65774A0C-1AD2-4E72-9D89-ACC77BE9CEB4@kernel.crashing.org>

On 9/29/06, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Sep 29, 2006, at 5:34 AM, Li Yang wrote:
>
> > Paul,
> >
> > The series of patches add generic QE infrastructure called
> > qe_lib, and MPC8360EMDS board support.  Qe_lib is used by
> > QE device drivers such as ucc_geth driver.
> >
> > This version updates QE interrupt controller to use new irq
> > mapping mechanism, addresses all the comments received with
> > last submission and includes some style fixes.
> >
> > v2: Change to use device tree for BCSR and MURAM;
> > Remove I/O port interrupt handling code as it is not generic
> > enough.
> >
> > v3: Address comments from Kumar;  Update definition of several
> > device tree nodes;  Copyright style change.
>
> In going through this code some general comments:
> * remove typedef's, its not the normal convention to use typedefs the
> way this code is.  Makes it more difficult to read
> * look at use of uint vs u32.  I think there are a number of cases
> were you really want u32.
>
> Also, can you provide some high level description of what all this
> code is doing.  I understand the port io init, I get the interrupt
> handling.  I'm at a loss as that what all the channel ucc_fast/
> ucc_slow code is trying to do and some of the init code.

Well, in brief.  There are many flexible options for QE SoC UCC.  Such
as clock routing, pin multiplexing, virtual fifo, BD rings, etc.   The
ucc code provides generic initialization and configuration routines
for these common options to be reused through drivers.  The
encapsulation of register manipulating code also makes the code more
readable.

- Leo

      reply	other threads:[~2006-09-29 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 10:34 [PATCH 0/9] Add support for QE and 8360EMDS board -v3 Li Yang
2006-09-29 14:15 ` Kumar Gala
2006-09-29 14:54   ` Li Yang [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=a0bc9bf80609290754s1ba72951m9825980b05025bef@mail.gmail.com \
    --to=leoli@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).