linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: galak@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] cpm: Describe multi-user ram in its own device node.
Date: Sat, 29 Sep 2007 00:30:05 +0400	[thread overview]
Message-ID: <20070929003005.59afc2a0@kernel.crashing.org> (raw)
In-Reply-To: <20070928190616.GB20213@loki.buserror.net>

Kumar,

Realizing this may suffer a bit from cleanest-dts flame war, but anyway I pretty much see a lot of
sense in getting this in during next merge window. Is this possible?

On Fri, 28 Sep 2007 14:06:16 -0500
Scott Wood wrote:

> The way the current CPM binding describes available multi-user (a.k.a.
> dual-ported) RAM doesn't work well when there are multiple free regions,
> and it doesn't work at all if the region doesn't begin at the start of
> the muram area (as the hardware needs to be programmed with offsets into
> this area).  The latter situation can happen with SMC UARTs on CPM2, as its
> parameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn't
> support moving it.
> 
> It is now described with a muram node, similar to QE.  The current CPM
> binding is sufficiently recent (i.e. never appeared in an official release)
> that compatibility with existing device trees is not an issue.
> 
> The code supporting the new binding is shared between cpm1 and cpm2, rather
> than remain separated.  QE should be able to use this code as well, once
> minor fixes are made to its device trees.
> 
> Signed-off-by: Scott Wood <scottwood@freescale.com>
Acked-by: Vitaly Bordug <vitb@kernel.crashing.org>

> ---
>  Documentation/powerpc/booting-without-of.txt |   40 ++++++-
>  arch/powerpc/Kconfig.debug                   |    6 +-
>  arch/powerpc/boot/cpm-serial.c               |   44 +++++--
>  arch/powerpc/boot/dts/ep88xc.dts             |   13 ++-
>  arch/powerpc/boot/dts/mpc8272ads.dts         |   11 ++
>  arch/powerpc/boot/dts/mpc885ads.dts          |   13 ++-
>  arch/powerpc/boot/dts/pq2fads.dts            |   13 ++-
>  arch/powerpc/sysdev/commproc.c               |   11 ++-
>  arch/powerpc/sysdev/cpm2_common.c            |   36 ++----
>  arch/powerpc/sysdev/cpm_common.c             |  159 ++++++++++++++++++++++++++
>  drivers/serial/cpm_uart/cpm_uart_cpm2.c      |    4 +-
>  include/asm-powerpc/commproc.h               |   12 ++
>  include/asm-powerpc/cpm.h                    |   14 +++
>  include/asm-powerpc/cpm2.h                   |   10 ++
>  14 files changed, 338 insertions(+), 48 deletions(-)

-- 
Sincerely, Vitaly

  parent reply	other threads:[~2007-09-28 20:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 19:06 [PATCH] cpm: Describe multi-user ram in its own device node Scott Wood
2007-09-28 20:06 ` Vitaly Bordug
2007-09-28 20:10   ` Scott Wood
2007-09-28 20:25     ` Vitaly Bordug
2007-09-28 20:30 ` Vitaly Bordug [this message]
2007-09-28 23:53   ` Kumar Gala
2007-09-29  6:49     ` Vitaly Bordug
2007-09-29 14:34       ` Kumar Gala
2007-10-01 16:10         ` Scott Wood
2007-10-02 14:43           ` Kumar Gala
2007-10-02 14:49             ` Timur Tabi
2007-10-02 15:49               ` Scott Wood
2007-10-02 15:51                 ` Timur Tabi
2007-10-02 15:51                   ` Scott Wood
2007-10-02 17:11                   ` Kumar Gala
2007-10-02 14:43 ` 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=20070929003005.59afc2a0@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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).