From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Question2: Determine subarch type
Date: Sun, 9 Dec 2012 10:13:59 +0000 [thread overview]
Message-ID: <20121209101358.GG14363@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20121209135551.f26ed91782f759add2cdf603@mail.ru>
On Sun, Dec 09, 2012 at 01:55:51PM +0400, Alexander Shiyan wrote:
> On Sun, 9 Dec 2012 09:51:38 +0000
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> > On Sun, Dec 09, 2012 at 10:51:17AM +0400, Alexander Shiyan wrote:
> > > How can we determine the sub-architecture type from the driver code?
> > > For example, we are building a multi-platform kernel for subarch A and B.
> > > One of the drivers should be used for subarch A only, and can not be used for
> > > subarch B. So, we need to avoid load this driver for other sub-architectures.
> > > Of course, we can check all machines in the subarch with machine_is_xx() macro,
> > > but I think that this is not the best way to do it.
> > > Do we have another way to do this?
> >
> > You control this by only registering the appropriate struct devices rather
> > than controlling this in the driver.
>
> Yes, but if driver is compiled as module?
Makes no difference.
next prev parent reply other threads:[~2012-12-09 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 6:51 Question2: Determine subarch type Alexander Shiyan
2012-12-09 9:51 ` Russell King - ARM Linux
2012-12-09 9:55 ` Alexander Shiyan
2012-12-09 10:13 ` Russell King - ARM Linux [this message]
2012-12-09 10:24 ` Alexander Shiyan
2012-12-09 14:40 ` Arnd Bergmann
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=20121209101358.GG14363@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