All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: bhanu jampala <adams.ppc@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: cpm_dpalloc questions
Date: Thu, 28 Aug 2008 11:23:35 -0500	[thread overview]
Message-ID: <48B6D107.30106@freescale.com> (raw)
In-Reply-To: <4a21eaea0808272212y6be97789nb6b94dd1d4987881@mail.gmail.com>

bhanu jampala wrote:
> I am working on MCC HDLC controller on MCC8260. I have two important questions:
> 
> 1. What is the range of DPRAM from which the cpm_dpalloc allocates memory?
>     How does the cpm_dpalloc work?

Assuming you're using arch/powerpc on a recent kernel version, it 
allocates from the memory specified in the muram node of the device tree.

>     I need this because, I need to reserve the DPRAM memory for MCC2
> from (128 * 60) to (255 * 60)
>     for channels ranging from 128 - 255.

Why do you need to reserve a specific address?

> 2. PROFF_SMC1 pointer placed at 0 , 64 offsets. is this not an area of
> MCC1 controller?

No, MCC1 PRAM starts at offset 0x8700.  Any other areas used are under 
software control.

>     how if I want to use the MCC channel on MCC1.
> 
>  In file include/asm-powerpc/cpm2.h.
> 
>  /* The SMCs are relocated to any of the first eight DPRAM pages.
>   * We will fix these at the first locations of DPRAM, until we
>   * get some microcode patches :-).
>   * The parameter ram space for the SMCs is fifty-some bytes, and
>   * they are required to start on a 64 byte boundary.
>   */
>  #define PROFF_SMC1      (0)
>  #define PROFF_SMC2      (64)

This is obsolete arch/ppc stuff and should be removed; the SMC pram is 
now dynamically allocated and relocated (and before that, it came from 
the device tree).

-Scott

  reply	other threads:[~2008-08-28 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  5:12 cpm_dpalloc questions bhanu jampala
2008-08-28 16:23 ` Scott Wood [this message]
2008-08-28 19:03   ` bhanu jampala
2008-08-29 21:25     ` bhanu jampala

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=48B6D107.30106@freescale.com \
    --to=scottwood@freescale.com \
    --cc=adams.ppc@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.