From: Scott Wood <scottwood@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com,
Vivek Mahajan <vivek.mahajan@freescale.com>
Subject: Re: [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram
Date: Wed, 21 Oct 2009 13:01:50 -0500 [thread overview]
Message-ID: <4ADF4C8E.3030209@freescale.com> (raw)
In-Reply-To: <20091021175012.ED29819F73@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Vivek Mahajan,
>
> In message <1256129459-10685-2-git-send-email-vivek.mahajan@freescale.com> you wrote:
>> Adds documentation for Freescale's QorIQ based cache-sram as under:-
>>
>> * How to enable it from a low level driver
>> * How to set its size
> ...
>> +The size of the above cache SRAM memory window is passed via the
>> +kernel command line as <cache-sram-size=....>
>
> Would it not make more sense to configure this property through the
> device tree?
The device tree describes the hardware. It is not a kernel config tree.
-Scott
next prev parent reply other threads:[~2009-10-21 18:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 12:50 [PATCH v3 1/3] powerpc/fsl: 85xx: document cache-sram size as a kernel parametric option Vivek Mahajan
2009-10-21 12:50 ` [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram Vivek Mahajan
2009-10-21 12:50 ` [PATCH v3 3/3] powerpc/fsl: 85xx: add cache-sram support Vivek Mahajan
2009-11-19 14:21 ` Kumar Gala
2009-11-19 14:29 ` Kumar Gala
2009-11-19 17:45 ` Scott Wood
2009-11-19 18:51 ` Kumar Gala
2009-11-20 6:45 ` Mahajan Vivek-B08308
2009-11-20 17:38 ` Scott Wood
2009-12-01 5:36 ` Mahajan Vivek-B08308
2009-12-01 17:04 ` Scott Wood
2009-12-02 3:26 ` Kumar Gala
2009-10-21 17:50 ` [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram Wolfgang Denk
2009-10-21 18:01 ` Scott Wood [this message]
2009-10-22 5:42 ` Mahajan Vivek-B08308
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=4ADF4C8E.3030209@freescale.com \
--to=scottwood@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=vivek.mahajan@freescale.com \
--cc=wd@denx.de \
/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.