From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] [orion] Move address map setup out of the drivers and into platform.
Date: Tue, 15 Nov 2011 08:41:22 +0100 [thread overview]
Message-ID: <20111115074122.GA2012@lunn.ch> (raw)
In-Reply-To: <alpine.LFD.2.02.1111141855340.3307@xanadu.home>
> I understand that you might want to get rid of the annoying platform
> data pointer for the mbus values. But I think that this could be done
> some other way though. IMHO the mbus initialization code for
> peripherals should remain in the drivers, and a different way to query
> the needed information be elaborated instead. Otherwise this is like
> throwing out the baby with the bath water.
I'm open to suggestion.
What do you think about the idea of keeping the first two patches,
i.e. *_mbus_dram_info out of mach-* and into plat-orion. Then
providing a function orion_mbus_dram_info() which returns its. Keep
the address map setup code in the drivers, remove struct
mbus_dram_target_info from platform_data and use this function
instead?
Thanks
Andrew
next prev parent reply other threads:[~2011-11-15 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 20:00 [PATCH 0/5] Move mbus setup code out of drivers and into platform Andrew Lunn
2011-11-12 20:00 ` [PATCH 1/5] [orion] Consolidate the address map setup on Orion based platforms Andrew Lunn
2011-11-12 20:00 ` [PATCH 2/5] [orion] Move the *_mbus_dram_info structure into the orion platform and call it orion_mbus_dram_info everywhere Andrew Lunn
2011-11-12 20:00 ` [PATCH 3/5] [orion] Move address map setup out of the drivers and into platform Andrew Lunn
2011-11-13 20:53 ` Michael Walle
2011-11-15 0:06 ` Nicolas Pitre
2011-11-15 7:41 ` Andrew Lunn [this message]
2011-11-15 22:14 ` Nicolas Pitre
2011-11-16 6:59 ` Andrew Lunn
2011-11-16 16:08 ` Nicolas Pitre
2011-11-16 16:49 ` Andrew Lunn
2011-11-16 17:18 ` Michael Walle
2011-11-16 17:25 ` Nicolas Pitre
2011-11-12 20:00 ` [PATCH 4/5] [orion] Remove address map info from all platform data strucutures Andrew Lunn
2011-11-12 20:00 ` [PATCH 5/5] [orion] Consolidate the address map setup code Andrew Lunn
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=20111115074122.GA2012@lunn.ch \
--to=andrew@lunn.ch \
--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).