From: Sascha Hauer <s.hauer@pengutronix.de>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 2/3] common: oftree: Add autoenable functionality
Date: Fri, 3 Nov 2017 09:47:13 +0100 [thread overview]
Message-ID: <20171103084713.xhmeukxxqqrt5jje@pengutronix.de> (raw)
In-Reply-To: <1509640782-8765-2-git-send-email-d.schultz@phytec.de>
On Thu, Nov 02, 2017 at 05:39:41PM +0100, Daniel Schultz wrote:
> This patch adds an API to automatically enable either hardware components
> with existing device drivers or i2c clients. All functions take a device
> tree path to find the hardware and will fix up the node status in the
> kernel device tree, if it's accessible.
>
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
> ---
> Changes:
> v2: Moved from standalone file to oftree.c
> Added of_device_is_available, if a driver is disabled
> Added of_property_read_u32
> Removed Kconfig
> Added of_ prefix to function names
> Renamed of_autoenable_i2c_by_path to of_autoenable_i2c_by_component
>
> common/oftree.c | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> include/of.h | 14 +++++++++
> 2 files changed, 106 insertions(+)
>
> diff --git a/common/oftree.c b/common/oftree.c
> index 09a4455..3b77a7e 100644
> --- a/common/oftree.c
> +++ b/common/oftree.c
> @@ -11,6 +11,7 @@
> #include <getopt.h>
> #include <init.h>
> #include <boot.h>
> +#include <i2c/i2c.h>
>
> #define MAX_LEVEL 32 /* how deeply nested we will go */
>
> @@ -260,3 +261,94 @@ struct fdt_header *of_get_fixed_tree(struct device_node *node)
>
> return fdt;
> }
> +
> +/**
> + * of_autoenable_device_by_path() - Autoenable a device by a device tree path
> + * @param path Device tree path up from the root to the device
> + * @return 0 on success, -enodev on failure. If no device found in the device
> + * tree.
> + *
> + * This function will search for a device and will enable it in the kernel
> + * device tree, if it exists and is loaded.
> + */
> +int of_autoenable_device_by_path(char *path)
> +{
> + struct device_d *device;
> + struct device_node *node;
> + int ret;
> +
> + node = of_find_node_by_name(NULL, path);
> + if (!node)
> + node = of_find_node_by_path(path);
> +
> + if (!node)
> + return -ENODEV;
> +
> + device = of_find_device_by_node(node);
> + if (!device)
> + if (!of_device_is_available(node))
> + return -ENODEV;
Is the of_find_device_by_node(node) test still necessary? In which case?
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-11-03 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 16:39 [PATCH v2 1/3] ARM: dts: AM335x: Add dummy i2c nodes Daniel Schultz
2017-11-02 16:39 ` [PATCH v2 2/3] common: oftree: Add autoenable functionality Daniel Schultz
2017-11-03 8:47 ` Sascha Hauer [this message]
2017-11-02 16:39 ` [PATCH v2 3/3] ARM: phytec-som-am335x: Add autoenable Daniel Schultz
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=20171103084713.xhmeukxxqqrt5jje@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=d.schultz@phytec.de \
/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