From: Scott Wood <scottwood@freescale•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH 3/3] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes
Date: Wed, 21 Nov 2007 11:33:08 -0600 [thread overview]
Message-ID: <20071121173308.GB4413@loki.buserror.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711202314030.24220@blarg.am.freescale.net>
On Tue, Nov 20, 2007 at 11:14:40PM -0600, Kumar Gala wrote:
> + - compatible : compatible list, contains 2 entries, first is
> + "fsl,CHIP-dma", where CHIP is the processor
> + (mpc8540, mpc8540, etc.) and the second is
> + "fsl,eloplus-dma"
So if the DMA register set gets tweaked again, will we have eloplusplus? :-)
Maybe elo2 would be better.
Do we really need completely separate descriptions of the two, or
can we just describe the difference in the compatible section?
-Scott
next prev parent reply other threads:[~2007-11-21 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 5:11 [PATCH 0/3] Device tree docs updates for FSL periphs Kumar Gala
2007-11-21 5:12 ` [PATCH 1/3] [POWERPC] Add docs for Freescale 83xx SATA device tree nodes Kumar Gala
2007-11-25 22:22 ` Arnd Bergmann
2007-11-26 15:41 ` Kumar Gala
2007-11-26 16:06 ` Arnd Bergmann
2007-12-03 2:37 ` Li Yang
2007-11-21 5:13 ` [PATCH 2/3] [POWERPC] Add docs for Freescale RapidIO device tree node Kumar Gala
2007-11-21 17:29 ` Scott Wood
2007-11-21 19:20 ` Kumar Gala
2007-11-21 5:14 ` [PATCH 3/3] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes Kumar Gala
2007-11-21 14:59 ` Timur Tabi
2007-11-21 15:33 ` Kumar Gala
2007-11-21 17:35 ` Scott Wood
2007-11-21 19:21 ` Kumar Gala
2007-11-21 19:27 ` Scott Wood
2007-11-21 22:28 ` David Gibson
2007-11-22 0:51 ` Timur Tabi
2007-11-26 15:44 ` Scott Wood
2007-11-22 0:49 ` Timur Tabi
2007-11-22 0:48 ` Timur Tabi
2007-11-21 17:33 ` Scott Wood [this message]
2007-11-21 19:19 ` Kumar Gala
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=20071121173308.GB4413@loki.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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