From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: mvebu: Device bus driver resurrection
Date: Tue, 26 Mar 2013 09:43:38 -0300 [thread overview]
Message-ID: <20130326124337.GD2454@localhost> (raw)
Hello everyone,
Now that we've all agreed on a mvebu mbus driver (or a first version of it)
I'd like to resurrect the Device Bus driver.
As far as I can remember, the last things said about this driver were:
* The timing parameters should be in {nano,pico,etc} seconds,
instead of ticks.
* Although not everyone agreed, this driver was a good thing to have
so we no longer depend on the bootloader setting these parameters.
* The address decoding windows should *not* be setup by this driver,
but rather be described in the device tree itself.
If anyone has aditional comments, please speak your mind.
My plan is to address all of the above comments, and send a v2 soon.
However, since we do not yet describe the address windows at the device tree,
the plan is to do window allocation/release in this devbus driver
**only as a temporal solution**.
Once the address decoding windows are properly described in the DTS,
we can remove that handling from the driver for good.
Does this sound sane enough?
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next reply other threads:[~2013-03-26 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 12:43 Ezequiel Garcia [this message]
2013-03-26 13:05 ` mvebu: Device bus driver resurrection Thomas Petazzoni
2013-03-26 16:45 ` Jason Gunthorpe
2013-03-26 16:55 ` Thomas Petazzoni
2013-04-05 21:26 ` Ezequiel Garcia
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=20130326124337.GD2454@localhost \
--to=ezequiel.garcia@free-electrons.com \
--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).