From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision
Date: Wed, 24 Jun 2015 22:01:38 -0700 [thread overview]
Message-ID: <20150625050138.GL4156@atomide.com> (raw)
In-Reply-To: <20150506114417.GI30910@pali>
* Pali Roh?r <pali.rohar@gmail.com> [150506 04:45]:
> On Wednesday 06 May 2015 13:04:01 Arnd Bergmann wrote:
> > >
> > > It needs to be done in this code, so "system_rev" variable is set
> > > properly...
> >
> > What I mean is which code accesses this variable that early?
> >
>
> ATAG code is doing it at same early stage, so I added it to same early
> stage...
Yes we should do this early like the other atags.
> > > > Also, it seems strange to have a string property and then use kstrtouint
> > > > to convert it into a number. I think it should either be specified in a DT
> > > > binding to be a string and then have the kernel not assume that it is a number,
> > > > or we should define it to be binary.
> > > >
> > > > Arnd
> > >
> > > Variable "system_rev" is number and it always was. So chaning type will
> > > break more parts.
> > >
> > > And it is string DT property to be human readable. Some other developers
> > > suggested for v2 to change it to string (from number).
> >
> > Both of them would be human readable, you just use something else to
> > read them ;-)
> >
> > If we have a string here, we should just change all uses of system_rev
> > in the kernel accordingly, there are only a few of them:
Let's just keep it as a hex as it was. After all it's an existing
interface in /proc that user space programs may expect to be in
hex format already.
Pali, care to repost the whole set again right after -rc1 with
with rev property naming and documentation added? Just keep it
as hex and let's forget any string conversion.
Regards,
Tony
next prev parent reply other threads:[~2015-06-25 5:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 8:49 [RESEND] [PATCH v2 0/2] ARM: /proc/cpuinfo: DT: Add support for Revision Pali Rohár
2015-05-06 8:49 ` [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision Pali Rohár
2015-05-06 9:31 ` Arnd Bergmann
2015-05-06 10:37 ` Pali Rohár
2015-05-06 11:04 ` Arnd Bergmann
2015-05-06 11:44 ` Pali Rohár
2015-06-25 5:01 ` Tony Lindgren [this message]
2015-06-25 7:18 ` Pali Rohár
2015-06-25 7:22 ` Tony Lindgren
2015-06-25 7:27 ` Pali Rohár
2015-06-25 7:41 ` Tony Lindgren
2015-07-06 12:23 ` Pali Rohár
2015-07-06 12:31 ` Tony Lindgren
2015-07-06 13:12 ` Pali Rohár
2015-07-06 13:55 ` Tony Lindgren
2015-07-06 15:22 ` Rob Herring
2015-07-06 16:20 ` Pali Rohár
2015-07-06 16:36 ` Pali Rohár
2015-07-06 17:30 ` Rob Herring
2015-07-06 15:20 ` Rob Herring
2015-07-06 15:24 ` Tony Lindgren
2015-06-25 10:03 ` Russell King - ARM Linux
2015-05-06 8:49 ` [RESEND] [PATCH v2 2/2] arm: boot: convert ATAG_REVISION to DT revision field Pali Rohár
2015-05-15 19:50 ` [PATCH 0/2] ARM: /proc/atags: Export also for DT Pali Rohár
2015-05-15 19:50 ` [PATCH 1/2] arm: devtree: Save atags if are in DT atags field Pali Rohár
2015-05-15 20:09 ` Arnd Bergmann
2015-06-25 5:06 ` Tony Lindgren
2015-05-15 19:50 ` [PATCH 2/2] arm: boot: store ATAG structure into " Pali Rohár
2015-05-15 20:12 ` Arnd Bergmann
2015-05-15 20:16 ` Pali Rohár
2015-05-15 20:21 ` Arnd Bergmann
2015-06-25 5:12 ` Tony Lindgren
2015-06-25 10:02 ` [PATCH 0/2] ARM: /proc/atags: Export also for DT Russell King - ARM Linux
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=20150625050138.GL4156@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).