All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>, "Nayak, Rajendra" <rnayak@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: hwmod and insertable modules
Date: Fri, 22 Oct 2010 09:59:49 -0700	[thread overview]
Message-ID: <87tyke6u4a.fsf@deeprootsystems.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593023461A7AC@dbde02.ent.ti.com> (Sanjeev Premi's message of "Fri, 22 Oct 2010 17:47:21 +0530")

"Premi, Sanjeev" <premi@ti.com> writes:

> I was trying other way - understand if there is an existing norm/
> convention that I can follow - rather than (re)invent it!

The existing norm is that omap_devices are never destroyed.  The same is
true for the way we handle platform_devices that are not omap_devices.
That being said, it doesn't answer the question of how we would destroy
them if we wanted to, and that does indeed deserve some discussion.

However, I think your confusion is more about the separation between
device code and driver code.

It is the responsibility of device init code (arch/arm/*omap*) to create
and register devices with the system.  This is where platform_devices
and omap_devices are handled currently.

The drivers then register themselves (as platform_drivers) with the
driver core, and the driver core hooks them together.

The goal we're working towards is that the drivers be generic, and
should not know anything about device-specific registration.

Kevin









      reply	other threads:[~2010-10-22 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  9:13 hwmod and insertable modules Premi, Sanjeev
2010-10-22  9:21 ` Premi, Sanjeev
2010-10-22  9:37 ` Nayak, Rajendra
2010-10-22  9:41   ` Premi, Sanjeev
2010-10-22  9:43     ` Nishanth Menon
2010-10-22 10:01       ` Premi, Sanjeev
2010-10-22 10:26         ` Nishanth Menon
2010-10-22 12:17           ` Premi, Sanjeev
2010-10-22 16:59             ` Kevin Hilman [this message]

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=87tyke6u4a.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=premi@ti.com \
    --cc=rnayak@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.