From: Sudeep Holla <sudeep.holla@arm.com>
To: Frank Rowand <frowand.list@gmail.com>, linux-kernel@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] of: base: add support to get machine model name
Date: Fri, 18 Nov 2016 10:41:10 +0000 [thread overview]
Message-ID: <075d4718-8cd2-e390-b755-bc24e7497eae@arm.com> (raw)
In-Reply-To: <582E1A59.7040502@gmail.com>
On 17/11/16 21:00, Frank Rowand wrote:
> On 11/17/16 07:32, Sudeep Holla wrote:
>> Currently platforms/drivers needing to get the machine model name are
>> replicating the same snippet of code. In some case, the OF reference
>> counting is either missing or incorrect.
>>
>> This patch adds support to read the machine model name either using
>> the "model" or the "compatible" property in the device tree root node
>> to the core OF/DT code.
>>
>> This can be used to remove all the duplicate code snippets doing exactly
>> same thing later.
>
> I find five instances of reading only property "model":
>
> arch/arm/mach-imx/cpu.c
> arch/arm/mach-mxs/mach-mxs.c
> arch/c6x/kernel/setup.c
> arch/mips/cavium-octeon/setup.c
> arch/sh/boards/of-generic.c
>
Ah sorry you were not Cc-ed in 2/2, but that shows all the instances
that this will be used for.
> I find one instance of reading property "model", then if
> that does not exist, property "compatible":
>
> arch/mips/generic/proc.c
>
Correct as you can check in patch 2/2
> The proposed patch matches the code used in one place, and thus
> current usage does not match the patch description.
>
Yes, but does it matter ? compatibles are somewhat informative about the
model IMO.
> Is my search bad? Are you planning to add additional instances
> of reading "model" then "compatible"?
>
No, just replacing the existing ones as in patch 2/2
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-11-18 10:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:32 Sudeep Holla
2016-11-17 15:32 ` [PATCH 2/2] of: base: replace all duplicate code with of_machine_get_model_name Sudeep Holla
2016-11-17 21:00 ` [PATCH 1/2] of: base: add support to get machine model name Frank Rowand
2016-11-17 22:12 ` Frank Rowand
2016-11-18 10:41 ` Sudeep Holla [this message]
2016-11-18 20:22 ` Frank Rowand
2016-11-21 16:05 ` Frank Rowand
2016-11-21 16:23 ` Sudeep Holla
2016-11-21 19:24 ` Frank Rowand
2016-11-21 20:49 ` Frank Rowand
2016-11-21 16:20 ` Sudeep Holla
2016-11-21 20:21 ` Frank Rowand
2016-11-18 14:46 ` Rob Herring
2016-11-18 20:00 ` Frank Rowand
2016-11-22 18:44 ` Frank Rowand
2016-11-22 21:35 ` Rob Herring
2016-11-23 10:25 ` Sudeep Holla
2016-12-09 16:03 ` Rob Herring
2016-12-09 23:54 ` Frank Rowand
2016-12-12 15:17 ` Rob Herring
2016-11-23 10:23 ` Sudeep Holla
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=075d4718-8cd2-e390-b755-bc24e7497eae@arm.com \
--to=sudeep.holla@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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
Powered by JetHome