From: Sascha Hauer <s.hauer@pengutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
lkml <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Vinay Simha BN <simhavcs@gmail.com>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
devicetree@vger.kernel.org,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [RFC][PATCH] misc: Introduce reboot_reason driver
Date: Wed, 9 Dec 2015 09:50:05 +0100 [thread overview]
Message-ID: <20151209085005.GR11966@pengutronix.de> (raw)
In-Reply-To: <CALAqxLU4y6+AsKcZSPUaJQ2BgcAWoT8OPcYO6EYfOz+-7r8FTQ@mail.gmail.com>
On Tue, Dec 08, 2015 at 04:13:35PM -0800, John Stultz wrote:
> On Tue, Dec 8, 2015 at 1:52 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > On Tuesday 08 December 2015 13:29:22 John Stultz wrote:
> >
> > > diff --git a/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts b/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts
> > > index 5183d18..ee5dcb7 100644
> > > --- a/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts
> > > +++ b/arch/arm/boot/dts/qcom-apq8064-nexus7-flo.dts
> > > @@ -282,6 +282,15 @@
> > > };
> > > };
> > >
> > > + reboot_reason: reboot_reason@2a03f65c {
> > > + compatible = "reboot_reason";
> >
> > This is not a good compatible string. There should generally be a vendor
> > name associated with it (use "linux," if nothing else, and you should have
> > '-' instead of '_'.
>
>
> Ack.
>
>
> >
> >
> > > + reg = <0x2A03F65C 0x4>;
> >
> > This may easily conflict with the device it is part of. We should have
> > non-overlapping register areas in general. For the example you are
> > looking at, which register block is this?
>
> So Bjorn says its IMEM, but I was assuming it was just a reserved
> magic phys addr from the bootloader.
>
> Ideally I'm hoping to use this same driver for another device, which
> plans to reserve a page from memory that the bootloader won't clear.
>
>
> > > +/* Types of reasons */
> > > +static enum {
> > > + NONE,
> > > + BOOTLOADER,
> > > + RECOVERY,
> > > + OEM,
> > > + MAX_REASONS
> > > +} __maybe_unused reason_types;
> >
> > The variable seems to always be unused, not just "__maybe_unused". Maybe remove it?
>
>
> Yea. I initially just had the empty enum, but the compiler was giving
> me "useless class storage specifier in empty declaration" warnings. So
> I added a variable to it, but then I got unused variable warnings. So
> I ended up with this. :P
>
> Is there a better way? Are enums for array indexes out of fashion?
They are not, but you have declared a variable (reason_types) which you
don't use. You probably meant to create a enum named reason_types, like
this:
enum reason_types {
NONE,
BOOTLOADER,
RECOVERY,
OEM,
MAX_REASONS
};
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 |
next prev parent reply other threads:[~2015-12-09 8:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 21:29 [RFC][PATCH] misc: Introduce reboot_reason driver John Stultz
2015-12-08 21:52 ` Arnd Bergmann
2015-12-08 22:15 ` Bjorn Andersson
2015-12-08 22:43 ` Rob Herring
2015-12-09 0:13 ` John Stultz
2015-12-09 8:50 ` Sascha Hauer [this message]
2015-12-09 21:42 ` John Stultz
2015-12-08 22:07 ` Bjorn Andersson
2015-12-09 0:22 ` John Stultz
2015-12-09 10:07 ` Arnd Bergmann
2015-12-10 1:19 ` John Stultz
2015-12-10 14:52 ` Arnd Bergmann
2015-12-10 18:56 ` John Stultz
2015-12-10 20:24 ` Rob Herring
2015-12-10 21:43 ` John Stultz
2015-12-10 22:11 ` Arnd Bergmann
2015-12-14 15:22 ` Rob Herring
2015-12-10 1:32 ` John Stultz
2015-12-10 9:05 ` Arnd Bergmann
2015-12-10 9:20 ` Tomas Winkler
2015-12-10 19:04 ` John Stultz
2015-12-10 19:57 ` One Thousand Gnomes
2015-12-10 20:03 ` John Stultz
2015-12-14 19:54 ` Bjorn Andersson
2015-12-08 22:26 ` Rob Herring
2015-12-09 0:34 ` John Stultz
2015-12-09 8:53 ` Sascha Hauer
2015-12-09 8:59 ` Sascha Hauer
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=20151209085005.GR11966@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=simhavcs@gmail.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