From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: overlapping resources for platform devices?
Date: Thu, 17 Nov 2005 15:49:25 +0000 [thread overview]
Message-ID: <20051117154925.GA26032@flint.arm.linux.org.uk> (raw)
In-Reply-To: <18C975E2-BA90-4595-8C50-63E5CFB9C0A1@kernel.crashing.org>
On Thu, Nov 17, 2005 at 09:36:38AM -0600, Kumar Gala wrote:
>
> On Nov 16, 2005, at 12:41 AM, Greg KH wrote:
>
> >On Tue, Nov 15, 2005 at 05:31:57PM -0600, Kumar Gala wrote:
> >>Guys,
> >>
> >>I was wondering if there was any issue in changing
> >>platform_device_add to
> >>use insert_resource instead of request_resource. The reason for this
> >>change is to handle several cases where we have device registers that
> >>overlap that two different drivers are handling.
> >>
> >>The biggest case of this is with ethernet on a number of PowerPC
> >>based
> >>systems where a subset of the ethernet controllers registers are
> >>used for
> >>MDIO/PHY bus control. We currently hack around the limitation by
> >>having
> >>the MDIO/PHY bus not actually register an memory resource region.
> >>
> >>If the following looks good I'll send a more formal patch.
> >
> >Looks good to me, but Russell knows this code much better than I.
> >
> >thanks,
> >
> >greg k-h
>
> Russell, any issues?
Haven't managed to look at this yet - busy catching up after illness.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-11-17 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 23:31 overlapping resources for platform devices? Kumar Gala
2005-11-16 6:41 ` Greg KH
2005-11-17 15:36 ` Kumar Gala
2005-11-17 15:49 ` Russell King [this message]
2005-11-23 6:57 ` Kumar Gala
2005-11-23 11:52 ` Russell King
2005-11-23 18:48 ` Kumar Gala
2005-11-23 22:30 ` Russell King
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=20051117154925.GA26032@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@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 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.