From: rananta@codeaurora.org
To: Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Trilok Soni <tsoni@codeaurora.org>,
Android Kernel Team <kernel-team@android.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: Add of_get_memory_prop()
Date: Wed, 18 Sep 2019 15:32:14 -0700 [thread overview]
Message-ID: <19d727bbfce08e59294920ba8097be7a@codeaurora.org> (raw)
In-Reply-To: <CAL_JsqJ2WeW0JHSHZuvo9bbc7JSFBr_qCuOp97i=b6Q+OPY7Cg@mail.gmail.com>
On 2019-09-18 13:13, Rob Herring wrote:
> On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
> <rananta@codeaurora.org> wrote:
>>
>> On some embedded systems, the '/memory' dt-property gets updated
>> by the bootloader (for example, the DDR configuration) and then
>> gets passed onto the kernel. The device drivers may have to read
>> the properties at runtime to make decisions. Hence, add
>> of_get_memory_prop() for the device drivers to query the requested
>
> Function name doesn't match. Device drivers don't need to access the
> FDT.
>
>> properties.
>>
>> Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
>> ---
>> drivers/of/fdt.c | 27 +++++++++++++++++++++++++++
>> include/linux/of_fdt.h | 1 +
>> 2 files changed, 28 insertions(+)
>
> We don't add kernel api's without users.
>
>>
>> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
>> index 223d617ecfe1..925cf2852433 100644
>> --- a/drivers/of/fdt.c
>> +++ b/drivers/of/fdt.c
>> @@ -79,6 +79,33 @@ void __init of_fdt_limit_memory(int limit)
>> }
>> }
>>
>> +/**
>> + * of_fdt_get_memory_prop - Return the requested property from the
>> /memory node
>> + *
>> + * On match, returns a non-zero positive value which represents the
>> property
>> + * value. Otherwise returns -ENOENT.
>> + */
>> +int of_fdt_get_memory_prop(const char *pname)
>> +{
>> + int memory;
>> + int len;
>> + fdt32_t *prop = NULL;
>> +
>> + if (!pname)
>> + return -EINVAL;
>> +
>> + memory = fdt_path_offset(initial_boot_params, "/memory");
>
> Memory nodes should have a unit-address, so this won't work frequently.
Sorry, can you please elaborate more on this? What do you mean by
unit-address and working frequently?
>
>> + if (memory > 0)
>> + prop = fdt_getprop_w(initial_boot_params, memory,
>> + pname, &len);
>> +
>> + if (!prop || len != sizeof(u32))
>> + return -ENOENT;
>> +
>> + return fdt32_to_cpu(*prop);
>> +}
>> +EXPORT_SYMBOL_GPL(of_fdt_get_memory_prop);
>> +
>> static bool of_fdt_device_is_available(const void *blob, unsigned
>> long node)
>> {
>> const char *status = fdt_getprop(blob, node, "status", NULL);
>> diff --git a/include/linux/of_fdt.h b/include/linux/of_fdt.h
>> index acf820e88952..537f29373358 100644
>> --- a/include/linux/of_fdt.h
>> +++ b/include/linux/of_fdt.h
>> @@ -38,6 +38,7 @@ extern char __dtb_end[];
>> /* Other Prototypes */
>> extern u64 of_flat_dt_translate_address(unsigned long node);
>> extern void of_fdt_limit_memory(int limit);
>> +extern int of_fdt_get_memory_prop(const char *pname);
>> #endif /* CONFIG_OF_FLATTREE */
>>
>> #ifdef CONFIG_OF_EARLY_FLATTREE
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
>>
- Raghavendra
next prev parent reply other threads:[~2019-09-18 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 18:46 [PATCH] of: Add of_get_memory_prop() Raghavendra Rao Ananta
2019-09-18 20:13 ` Rob Herring
2019-09-18 22:32 ` rananta [this message]
2019-10-01 22:09 ` Rob Herring
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=19d727bbfce08e59294920ba8097be7a@codeaurora.org \
--to=rananta@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tsoni@codeaurora.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).