From: Benoit Cousson <b-cousson@ti.com>
To: khilman@ti.com
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
grant.likely@secretlab.ca, Benoit Cousson <b-cousson@ti.com>
Subject: [PATCH v3 0/2] OMAP: omap_device: Add a method to build an omap_device from a DT node
Date: Thu, 22 Sep 2011 22:52:23 +0200 [thread overview]
Message-ID: <1316724745-24896-1-git-send-email-b-cousson@ti.com> (raw)
Hi Kevin,
This is the updated version of the initial series that introduced a
notifier in order to create an omap_device from a platform_device bound
to DT node as suggested by Grant.
For the moment, the informations are all extracted from the hwmod data.
The idea is to focus first on the devices / board static init removal.
The other issue is that some bindings, like dma, are still not present
in the DT core code. The reg and irq bindings are there, but cannot
be used by some drivers due to the lack of named resources in DT for
the moment.
We agreed with Grant about the strategy to introduce the name without
breaking the compatibility and the default assumption about the order.
I'll update that in another series after 3.2 and then these informations
will be moved from hwmod to DT.
Patches are based on my for_3.2/1_omap_device_cleanup branch and are
available here:
git://gitorious.org/omap-pm/linux.git for_3.2/2_omap_device_dt
It is tested on OMAP4 SDP, Panda and Beagle-xM with and without CONFIG_OF.
Regards,
Benoit
Changes since v1: http://www.spinics.net/lists/linux-omap/msg55814.html
- delete omap_device structure during BUS_NOTIFY_DEL_DEVICE callback
as suggested by Kevin
- merge previous patches 2&3 as suggested by Kevin
- delete pm_lats in omap_device_delete since this is now kmalloc-ed
- use kmemdup instead of kzalloc + memcopy for hmwods creation
- Fix the wrong usage of of_*.h includes to build properly without
CONFIG_OF.
Changes since v2: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg55892.html
- Add binding documentation for the OMAP attributes
- Add "ti," prefix to hwmods and no_idle_on_suspend attributes
- Change the static init of the notifier_block structure as suggested by Grant
- Add a comment to remove the helpers once the generic one from swarren will
be merged
Benoit Cousson (2):
OMAP: omap_device: Add omap_device_[alloc|delete] for DT integration
OMAP: omap_device: Add a method to build an omap_device from a DT node
.../devicetree/bindings/arm/omap/omap.txt | 42 +++
arch/arm/plat-omap/omap_device.c | 322 ++++++++++++++++----
2 files changed, 306 insertions(+), 58 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/omap/omap.txt
next reply other threads:[~2011-09-22 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 20:52 Benoit Cousson [this message]
2011-09-22 20:52 ` [PATCH v3 1/2] OMAP: omap_device: Add omap_device_[alloc|delete] for DT integration Benoit Cousson
2011-09-22 20:52 ` [PATCH v3 2/2] OMAP: omap_device: Add a method to build an omap_device from a DT node Benoit Cousson
2011-09-27 1:46 ` Grant Likely
2011-09-27 16:04 ` Cousson, Benoit
2011-09-28 16:11 ` Cousson, Benoit
2011-09-28 17:47 ` Kevin Hilman
2011-09-29 17:30 ` Grant Likely
2011-09-29 20:46 ` Kevin Hilman
2011-09-26 22:38 ` [PATCH v3 0/2] " Kevin Hilman
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=1316724745-24896-1-git-send-email-b-cousson@ti.com \
--to=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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