mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] platform driver: Drop check for resource conflicts
Date: Wed, 10 Oct 2012 18:48:09 +0200	[thread overview]
Message-ID: <20121010164809.GC27665@pengutronix.de> (raw)
In-Reply-To: <20121010105743.GA13639@game.jcrosoft.org>

On Wed, Oct 10, 2012 at 12:57:43PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:44 Wed 10 Oct     , Sascha Hauer wrote:
> > The check is wrong since it would have to check whether the
> > new iomem region overlaps with an existing region. Checking
> > for the base address only is not enough.
> > Currently this is not possible because every device conflicts
> > with the top iomem region which covers the whole address space.
> > 
> > This at least fixes the regression that devices whose memory region
> > begins at 0x0 can no longer be succesfully registered.
> > 
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > Cc: Alexander Shiyan <shc_work@mail.ru>
> > Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > ---
> >  drivers/base/platform.c |   12 ------------
> >  1 file changed, 12 deletions(-)
> > 
> > diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> > index 13b4620..ea4e37b 100644
> > --- a/drivers/base/platform.c
> > +++ b/drivers/base/platform.c
> > @@ -66,18 +66,6 @@ int platform_device_register(struct device_d *new_device)
> >  {
> >  	new_device->bus = &platform_bus;
> >  
> > -	if (new_device->resource) {
> > -		struct device_d *dev;
> > -
> > -		bus_for_each_device(new_device->bus, dev) {
> > -			if (!dev->resource)
> > -				continue;
> > -			if (dev->resource->start == new_device->resource->start) {
> > -				return -EBUSY;
> > -			}
> > -		}
> > -	}
> > -
> IIRC this break the dt probe no?

Why should it?

> 
> this break the arm and st hw atleast

What breaks it? The check for conflicts or the removal of the check?
What breaks? I know no board which registers conflicting resources, so
the check never triggers.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2012-10-10 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  9:44 Sascha Hauer
2012-10-10 10:57 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-10 16:48   ` Sascha Hauer [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=20121010164809.GC27665@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=plagnioj@jcrosoft.com \
    /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