From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@gate.crashing.org>
Cc: linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Platform device model drawback
Date: Tue, 15 Nov 2005 14:40:56 -0800 [thread overview]
Message-ID: <20051115224056.GA14357@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0511151332310.28098-100000@gate.crashing.org>
On Tue, Nov 15, 2005 at 01:34:47PM -0600, Kumar Gala wrote:
> > You only register the driver once. The individual devices can be bound
> > to the same driver, right?
> >
> > > Not registering it in CPM_UART, how the pdev could be obtained?
> > >
> > > Maybe this is clear, but platform stuff is cumbersome some times...
> >
> > Then make it cleaner :)
>
> This is where the confusion is. We have two instances of device A. We
> want instance 1 of device A bound to driver "enet" and instance 2 of
> device A bound to "serial".
That's different from what was described earlier :)
In this case, you need two different struct devices.
> Today both instances are called "deviceA". However we can't register two
> different drivers as "deviceA".
Nor would you want to.
> Not sure if that clarifies the issue any.
A bit. I think it still sounds messy...
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-15 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 16:51 Platform device model drawback Vitaly Bordug
2005-11-15 16:55 ` Greg KH
2005-11-15 17:59 ` Vitaly Bordug
2005-11-15 17:59 ` Greg KH
2005-11-15 19:34 ` Kumar Gala
2005-11-15 22:40 ` Greg KH [this message]
[not found] ` <50e923300511161839g12ad1e88je46f989192cd3f58@mail.google.com>
[not found] ` <20051117041645.GA19145@kroah.com>
2005-11-17 17:51 ` Peter Hanson
2005-11-17 17:49 ` Greg KH
2005-11-17 23:05 ` Peter Hanson
2005-11-17 23:46 ` Grant Likely
2005-11-18 23:47 ` Greg KH
2005-11-19 2:37 ` Grant Likely
2005-11-15 19:43 ` Andy Fleming
2005-11-15 19:41 ` Andrey Volkov
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=20051115224056.GA14357@kroah.com \
--to=greg@kroah.com \
--cc=galak@gate.crashing.org \
--cc=linuxppc-embedded@ozlabs.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).