From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] drivers/base: Generic framework for tracking internal interfaces
Date: Thu, 1 May 2014 10:11:02 +0100 [thread overview]
Message-ID: <20140501091102.GF26756@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5361F1F3.7070005@wp.pl>
On Thu, May 01, 2014 at 09:04:19AM +0200, Andrzej Hajda wrote:
> 2. You replace calls of component_add and component_del with calls
> to interface_tracker_ifup(dev, INTERFACE_TRACKER_TYPE_COMPONENT,
> &specific_component_ops),
> or interface_tracker_ifdown.
> Thats all for components.
How does the master get to decide which components are for it? As
I see it, all masters see all components of a particular "type".
What if you have a system with two masters each of which are bound
to a set of unique components but some of the components are of a
the same type?
How does the master know what "type" to use?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-05-01 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 14:02 [RFC PATCH 0/4] drivers/base: Generic framework for tracking internal interfaces Andrzej Hajda
2014-04-30 14:02 ` [RFC PATCH 1/4] drivers/base: add interface tracker framework Andrzej Hajda
2014-04-30 14:02 ` [RFC PATCH 2/4] drm/panel: add interface tracker support Andrzej Hajda
2014-04-30 14:02 ` [RFC PATCH 3/4] drm/exynos/dpi: " Andrzej Hajda
2014-04-30 14:02 ` [RFC PATCH 4/4] drm/panel/ld9040: do not power off panel on removal Andrzej Hajda
2014-04-30 15:49 ` [RFC PATCH 0/4] drivers/base: Generic framework for tracking internal interfaces Greg Kroah-Hartman
2014-04-30 21:42 ` Andrzej Hajda
2014-04-30 22:28 ` Russell King - ARM Linux
2014-05-01 7:04 ` Andrzej Hajda
2014-05-01 9:11 ` Russell King - ARM Linux [this message]
2014-05-05 7:38 ` Andrzej Hajda
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=20140501091102.GF26756@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).