linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Grant Likely <grant.likely@linaro.org>,
	Arnd Bergmann <arnd@linaro.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	Darren Hart <dvhart@infradead.org>
Subject: Re: [PATCH 2/2] device property: Introduce firmware node type for platform data
Date: Fri, 3 Apr 2015 16:06:57 +0200	[thread overview]
Message-ID: <20150403140657.GC12376@kroah.com> (raw)
In-Reply-To: <3619014.N4Tg0UgJKE@vostro.rjw.lan>

On Fri, Apr 03, 2015 at 04:05:11PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Introduce data structures and code allowing "built-in" properties
> to be associated with devices in such a way that they will be used
> by the device_property_* API if no proper firmware node (neither DT
> nor ACPI) is present for the given device.
> 
> Each property is to be represented by a property_entry structure.
> An array of property_entry structures (terminated with a null
> entry) can be pointed to by the properties field of struct
> property_set that can be added as a firmware node to a struct
> device using device_add_property_set().  That will cause the
> device_property_* API to use that property_set as the source
> of properties if the given device does not have a DT node or
> an ACPI companion device object associated with it.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Tested-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> 
> Greg, any objections?

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2015-04-03 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 13:17 [resend PATCH] driver core: property: support for generic property Heikki Krogerus
2015-03-09 14:43 ` Heikki Krogerus
2015-03-12  1:41 ` Rafael J. Wysocki
2015-03-13 15:10   ` Grant Likely
2015-03-13 15:24     ` Arnd Bergmann
2015-03-14  1:09       ` Rafael J. Wysocki
2015-03-14  9:42         ` Greg Kroah-Hartman
2015-03-16  9:47           ` Grant Likely
2015-03-16 22:59             ` Rafael J. Wysocki
2015-03-17 14:17               ` [PATCH] ACPI: Introduce has_acpi_companion() Rafael J. Wysocki
2015-03-22 23:10               ` [PATCH] driver core: Implement device property accessors through fwnode ones Rafael J. Wysocki
2015-03-23 20:13                 ` Greg Kroah-Hartman
2015-03-28  1:05               ` [PATCH 0/3] device property: support for "built-in" properties Rafael J. Wysocki
2015-03-28  1:09                 ` [PATCH 1/3] device property: Make it possible to use secondary firmware nodes Rafael J. Wysocki
2015-03-28  1:10                 ` [PATCH 2/3] device property: Introduce firmware node type for platform data Rafael J. Wysocki
2015-03-28  1:26                 ` [PATCH 3/3][RFD] device property: Implement fallback to built-in properties Rafael J. Wysocki
2015-04-02 14:35                   ` Heikki Krogerus
2015-04-03 13:59                     ` Rafael J. Wysocki
2015-04-03 14:01                 ` [PATCH 0/2] device property: firmware node type for platform data Rafael J. Wysocki
2015-04-03 14:03                   ` [PATCH 1/2] device property: Make it possible to use secondary firmware nodes Rafael J. Wysocki
2015-04-03 14:06                     ` Greg Kroah-Hartman
2015-04-03 14:05                   ` [PATCH 2/2] device property: Introduce firmware node type for platform data Rafael J. Wysocki
2015-04-03 14:06                     ` Greg Kroah-Hartman [this message]
2015-03-16  7:25   ` [resend PATCH] driver core: property: support for generic property Heikki Krogerus

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=20150403140657.GC12376@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@linaro.org \
    --cc=dvhart@infradead.org \
    --cc=grant.likely@linaro.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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).