From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Should we pass amba device peripheral id with device structure or not?
Date: Mon, 24 May 2010 23:32:02 +0100 [thread overview]
Message-ID: <20100524223202.GA21923@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTinQqEIs3PDWJGFwYqsBZxANmrbH_xOtOchK5Nlh@mail.gmail.com>
On Tue, May 25, 2010 at 12:17:02AM +0200, Linus Walleij wrote:
> [Russell]
> We'd have to add a proper bus clock to all PrimeCells to have this in
> some sane state I believe.
That's basically what I'm saying. At the bus/driver level, we need to
deal with the bus clock dependency separately from the peripheral clock
if the bus clock can be shut off.
I had originally anticipated that all primecells on a bus would have
their bus clock fed from a common unmaskable source, and that shutting
off the bus clock to the primecell would be a very bad thing to happen
to the bus - but it seems that it's permitted after all.
This will be trivial to deal with for clkdev-based platforms... The
non-clkdev are an entirely separate proposition - but I don't think we
have any primecell-using platforms which don't use clkdev.
next prev parent reply other threads:[~2010-05-24 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 7:02 Should we pass amba device peripheral id with device structure or not? Viresh KUMAR
2010-05-14 14:25 ` Catalin Marinas
2010-05-21 19:38 ` Russell King - ARM Linux
2010-05-24 4:38 ` Viresh KUMAR
2010-05-24 21:32 ` Russell King - ARM Linux
2010-05-24 22:17 ` Linus Walleij
2010-05-24 22:32 ` Russell King - ARM Linux [this message]
2010-05-26 8:27 ` Viresh KUMAR
2010-05-24 21:51 ` Linus Walleij
2010-05-24 20:14 ` Linus Walleij
2010-05-26 8:30 ` Viresh KUMAR
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=20100524223202.GA21923@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).