From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] ARM: EXYNOS: initial board support for exynos5260 SoC
Date: Tue, 18 Feb 2014 12:55:46 +0100 [thread overview]
Message-ID: <3872362.HBjU7v1oSg@wuerfel> (raw)
In-Reply-To: <CAK9yfHwcteO78JG4OhRZtMcpAd-aN85sxqELJ3ZLW0D0PXoZ7w@mail.gmail.com>
On Tuesday 18 February 2014 17:11:43 Sachin Kamat wrote:
> On 18 February 2014 16:33, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 18 February 2014 16:27:54 Rahul Sharma wrote:
> >>
> >> +static struct map_desc exynos5260_iodesc[] __initdata = {
> >> + {
> >> + .virtual = (unsigned long)S5P_VA_SYSRAM_NS,
> >> + .pfn = __phys_to_pfn(EXYNOS5260_PA_SYSRAM_NS),
> >> + .length = SZ_4K,
> >> + .type = MT_DEVICE,
> >> + },
> >> +};
> > As I commented before, I think we really shouldn't do this any more: There
> > is no excuse why you still need to add SoC specific code here. Please put
> > the SYSRAM into DT and make a proper abstraction for it so you don't have
> > to modify the kernel every time a new SoC variant comes out.
>
> Do we have any bindings already defined for this kind of stuff or is
> this implemented in
> any other platform/architecture for reference?
>
It depends on how the sram is used. There is a generic binding in
Documentation/devicetree/bindings/misc/sram.txt that may be appropriate here.
Arnd
next prev parent reply other threads:[~2014-02-18 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:57 [PATCH v4 0/3] exynos: arch: add support for exynos5260 SoC Rahul Sharma
2014-02-18 10:57 ` [PATCH v4 1/3] ARM: EXYNOS: initial board " Rahul Sharma
2014-02-18 11:03 ` Arnd Bergmann
2014-02-18 11:41 ` Sachin Kamat
2014-02-18 11:55 ` Arnd Bergmann [this message]
2014-02-18 10:57 ` [PATCH v4 2/3] ARM: dts: add dts files " Rahul Sharma
2014-02-18 10:57 ` [PATCH v4 3/3] ARM: dts: add dts files for xyref5260 board Rahul Sharma
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=3872362.HBjU7v1oSg@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).