From: Sam Ravnborg <sam@ravnborg.org>
To: Alexander Kurz <akurz@blala.de>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>, barebox@lists.infradead.org
Subject: Re: [PATCH] gpiolib: fix: do not access oftree on non-OFDEVICE boards
Date: Wed, 5 Jul 2017 20:22:10 +0200 [thread overview]
Message-ID: <20170705182210.GA13920@ravnborg.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1707042212240.19314@blala.de>
On Tue, Jul 04, 2017 at 10:17:39PM +0200, Alexander Kurz wrote:
> Hi Lucas,
>
> On Mon, 3 Jul 2017, Lucas Stach wrote:
>
> > Am Sonntag, den 02.07.2017, 22:24 +0200 schrieb Alexander Kurz:
> > > Non-OFDEVICE boards may have OFTREE=y set, e.g. by BOOTM_OFTREE.
> > > Attempts to browse the oftree will crash barebox on those boards.
> > >
> > > Signed-off-by: Alexander Kurz <akurz@blala.de>
> > > ---
> > > drivers/gpio/gpiolib.c | 5 ++++-
> > > 1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > > index a3e17ad..a1ff965 100644
> > > --- a/drivers/gpio/gpiolib.c
> > > +++ b/drivers/gpio/gpiolib.c
> > > @@ -416,7 +416,10 @@ int gpiochip_add(struct gpio_chip *chip)
> > > for (i = chip->base; i < chip->base + chip->ngpio; i++)
> > > gpio_desc[i].chip = chip;
> > >
> > > - return of_gpiochip_scan_hogs(chip);
> > > + if (IS_ENABLED(CONFIG_OFDEVICE))
> > > + return of_gpiochip_scan_hogs(chip);
> > > + else
> > > + return 0;
> >
> > This may also crash in mixed oftree/board file based systems (however
> > unlikely that is). I think an early return from of_gpiochip_scan_hogs ()
> > if chip->dev->device_node is NULL would be more robust.
> IS_ENABLED(...) is evaluated at compile time.
> Checking CONFIG_OFDEVICE even before calling the OF-function gives the
> compiler the chance to omit the integration of the unneeded function.
> A quick test on with kindle3_defconfig resulted in half a kilobyte
> image size difference.
I have incorporat this change in the fix I posted, and added your
Signed-off-by: as you posted this first and my change came on
top of yours.
Will post in a new thread.
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-07-05 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 20:24 Alexander Kurz
2017-07-03 9:56 ` Lucas Stach
2017-07-04 20:17 ` Alexander Kurz
2017-07-05 18:22 ` Sam Ravnborg [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=20170705182210.GA13920@ravnborg.org \
--to=sam@ravnborg.org \
--cc=akurz@blala.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@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