All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 08/10] device property: add fwnode_is_compatible()
Date: Thu, 02 Jul 2015 01:44:46 +0200	[thread overview]
Message-ID: <2059631.9RN3FXDI12@vostro.rjw.lan> (raw)
In-Reply-To: <1435676108-20590-9-git-send-email-tomeu.vizoso@collabora.com>

On Tuesday, June 30, 2015 04:55:06 PM Tomeu Vizoso wrote:
> This is being added so code that is independent of the firmware being
> used can match firmware nodes to devices.
> 
> This commit only implements it for OF nodes.
> 
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>

I don't really like this one, as it is hiding OF-specific stuff under
a seemingly generic API.

The "compatible" property also makes sense for certain ACPI device objects
nowadays, so at least this should take that case into accout.

What do you need it for, specifically?


> ---
> 
>  drivers/base/property.c  | 9 +++++++++
>  include/linux/property.h | 2 ++
>  2 files changed, 11 insertions(+)
> 
> diff --git a/drivers/base/property.c b/drivers/base/property.c
> index 92cdbb3..9c8be31 100644
> --- a/drivers/base/property.c
> +++ b/drivers/base/property.c
> @@ -585,3 +585,12 @@ const char *fwnode_get_name(struct fwnode_handle *fwnode)
>  	return NULL;
>  }
>  EXPORT_SYMBOL_GPL(fwnode_get_name);
> +
> +bool fwnode_is_compatible(struct fwnode_handle *fwnode, const char *compatible)
> +{
> +	if (is_of_node(fwnode))
> +		return of_device_is_compatible(to_of_node(fwnode), compatible);
> +
> +	return false;
> +}
> +EXPORT_SYMBOL_GPL(fwnode_is_compatible);
> diff --git a/include/linux/property.h b/include/linux/property.h
> index cfd1eb2..bf10074 100644
> --- a/include/linux/property.h
> +++ b/include/linux/property.h
> @@ -80,6 +80,8 @@ const char *fwnode_get_name(struct fwnode_handle *fwnode);
>  
>  void fwnode_handle_put(struct fwnode_handle *fwnode);
>  
> +bool fwnode_is_compatible(struct fwnode_handle *fwnode, const char *compatible);
> +
>  unsigned int device_get_child_node_count(struct device *dev);
>  
>  static inline bool device_property_read_bool(struct device *dev,
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2015-07-01 23:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 14:54 [PATCH v1 0/10] Fixes and API additions for firmware nodes Tomeu Vizoso
2015-06-30 14:54 ` [PATCH v1 01/10] of/platform: Set fwnode field for new devices Tomeu Vizoso
2015-06-30 18:24   ` Grant Likely
2015-06-30 18:24     ` Grant Likely
2015-07-01 23:32   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 02/10] i2c: core: Have clients point to their firmware nodes Tomeu Vizoso
2015-06-30 14:55   ` Tomeu Vizoso
2015-07-31 10:36   ` Wolfram Sang
2015-07-31 10:36     ` Wolfram Sang
2015-08-06 14:17     ` Tomeu Vizoso
2015-08-06 14:17       ` Tomeu Vizoso
2015-08-06 21:06       ` Wolfram Sang
2015-08-06 21:06         ` Wolfram Sang
2015-06-30 14:55 ` [PATCH v1 03/10] mfd: Have child devices " Tomeu Vizoso
2015-06-30 18:24   ` Grant Likely
2015-07-01  7:36   ` Lee Jones
2015-07-01 23:33   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 04/10] device property: add fwnode_get_parent() Tomeu Vizoso
2015-07-01 23:38   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 05/10] device property: add fwnode_get_name() Tomeu Vizoso
2015-06-30 18:26   ` Grant Likely
2015-07-01 23:38   ` Rafael J. Wysocki
2015-07-22 11:53     ` Tomeu Vizoso
2015-06-30 14:55 ` [PATCH v1 06/10] ACPI / scan: Add acpi_dev_get_next_child() Tomeu Vizoso
2015-07-01 23:39   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 07/10] device property: Add fwnode_get_next_child_node() Tomeu Vizoso
2015-07-01 23:40   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 08/10] device property: add fwnode_is_compatible() Tomeu Vizoso
2015-06-30 18:28   ` Grant Likely
2015-07-01 23:44   ` Rafael J. Wysocki [this message]
2015-06-30 14:55 ` [PATCH v1 09/10] device: property: add fwnode_driver_match_device() Tomeu Vizoso
2015-06-30 18:32   ` Grant Likely
2015-07-01 23:45   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 10/10] core: platform: use fwnode_driver_match_device() Tomeu Vizoso
2015-07-01 23:46   ` Rafael J. Wysocki
2015-07-10 12:53     ` Tomeu Vizoso
2015-07-11  2:47       ` Rafael J. Wysocki
2015-07-13  6:55         ` Tomeu Vizoso
2015-06-30 15:32 ` [PATCH v1 0/10] Fixes and API additions for firmware nodes Rafael J. Wysocki
2015-07-01  6:47 Tomeu Vizoso
2015-07-01  6:48 ` [PATCH v1 08/10] device property: add fwnode_is_compatible() Tomeu Vizoso

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=2059631.9RN3FXDI12@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomeu.vizoso@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.