public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Mike Frysinger <vapier@gentoo.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: simplify platform_get_resource()
Date: Tue, 28 Jul 2009 09:31:21 -0700	[thread overview]
Message-ID: <20090728163121.GB13741@suse.de> (raw)
In-Reply-To: <20090728105949.GA16458@rakim.wolfsonmicro.main>

On Tue, Jul 28, 2009 at 11:59:49AM +0100, Mark Brown wrote:
> On Mon, Jul 27, 2009 at 02:20:56PM -0400, Mike Frysinger wrote:
> > The platform_get_resource() function takes a number for the desired index
> > into the resource array, but then does a for loop on the array to get to
> > that index.  Considering the array is linear, the loop overhead is just
> > that -- overhead.  So unless I missed something, convert it into an index
> > check and access the desired resource directly.  Resulting code makes a
> > lot more sense considering its purpose.
> 
> This showed up in linux-next for me today and is causing breakage on at
> least S3C64xx platforms since it changes the resource numbering when
> there's more than one resource type for a device:
> 
> > -	for (i = 0; i < dev->num_resources; i++) {
> > -		struct resource *r = &dev->resource[i];
> > -
> > -		if (type == resource_type(r) && num-- == 0)
> > +	if (num >= 0 && num < dev->num_resources) {
> > +		struct resource *r = &dev->resource[num];
> > +		if (type == resource_type(r))
> 
> Previously the resources were indexed within their type (so you'd get
> I/O resources 0, 1, ..., IRQ resources 0, 1, ... and so on) but now the
> index treats all the resources for a device as a single array, causing
> them to be renumbered for callers.
> 
> This causes drivers doing lookups by number to fail to find their
> resources and not probe, causing widespread breakage.  Reverting the
> patch fixes the problem.

I've now dropped this patch.

thanks,

greg k-h

      reply	other threads:[~2009-07-28 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 18:20 [PATCH] driver core: simplify platform_get_resource() Mike Frysinger
2009-07-28 10:59 ` Mark Brown
2009-07-28 16:31   ` Greg KH [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=20090728163121.GB13741@suse.de \
    --to=gregkh@suse.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier@gentoo.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