From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>, Al Stone <ahs3@redhat.com>
Subject: Re: [PATCH v3 3/4] device property: Move FW type specific functionality to FW specific files
Date: Tue, 21 Mar 2017 10:27:06 +0200 [thread overview]
Message-ID: <1655370d-6867-9466-6d26-f34a09789369@linux.intel.com> (raw)
In-Reply-To: <CAL_Jsq+HGNCbiHw8dD0R+zj+GfGxaypk7di0sbxNr4bZsjqxbA@mail.gmail.com>
Hi Rob,
Rob Herring wrote:
> On Thu, Mar 16, 2017 at 8:34 AM, Sakari Ailus
> <sakari.ailus@linux.intel.com> wrote:
>> The device and fwnode property API supports Devicetree, ACPI and pset
>> properties. The implementation of this functionality for each firmware
>> type was embedded in the fwnode property core. Move it out to firmware
>> type specific locations, making it easier to maintain.
>>
>> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>> ---
>> drivers/acpi/property.c | 87 +++++++++++++++
>> drivers/acpi/scan.c | 1 +
>> drivers/base/property.c | 280 +++++++++++++++++++-----------------------------
>> drivers/of/base.c | 99 +++++++++++++++++
>
> This is the opposite direction everything else has been moving. For
> example, I2C parsing is in drivers/i2c. But I guess this is a bit
> different.
>
> In any case, please move this to drivers/of/property.c (and perhaps
> move all of of_property_* there too).
Ok.
There appear to be quite a few functions dealing with properties in
drivers/of/base.c either directly reading their values or otherwise
accessing them. Let me see if I can find a roughly coherent set of
functions to move to property.c. I'll move the existing functions there
first, creating a new patch before this one.
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2017-03-21 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:34 [PATCH v3 0/4] Move firmware specific code to firmware specific locations Sakari Ailus
2017-03-16 13:34 ` [PATCH v3 1/4] device property: Read strings using string array reading functions Sakari Ailus
2017-03-16 13:34 ` [PATCH v3 2/4] device property: Implement fwnode_get_next_parent() using fwnode interface Sakari Ailus
[not found] ` <1489671289-20406-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-16 13:34 ` [PATCH v3 3/4] device property: Move FW type specific functionality to FW specific files Sakari Ailus
2017-03-20 20:57 ` Rob Herring
2017-03-21 8:27 ` Sakari Ailus [this message]
2017-03-21 8:28 ` Sakari Ailus
2017-03-16 13:34 ` [PATCH v3 4/4] device property: Move fwnode graph ops to firmware specific locations Sakari Ailus
[not found] ` <1489671289-20406-5-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-20 21:15 ` Rob Herring
2017-03-21 10:54 ` Sakari Ailus
2017-03-21 11:17 ` Sakari Ailus
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=1655370d-6867-9466-6d26-f34a09789369@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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 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).