From: Sinan Kaya <okaya@codeaurora.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
devicetree@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V6 3/7] device property: Introduce a common API to fetch device match data
Date: Thu, 7 Dec 2017 15:15:29 -0500 [thread overview]
Message-ID: <74f88482-71ff-db72-ee6e-cc9b3b0bc37e@codeaurora.org> (raw)
In-Reply-To: <20171207122948.yyl6adb6lnb56gok@valkosipuli.retiisi.org.uk>
On 12/7/2017 7:29 AM, Sakari Ailus wrote:
> Hi Sinan,
>
> Thanks for the update.
>
> Just one small comment below.
>
[snip]
>>
>> struct fwnode_handle {
>> struct fwnode_handle *secondary;
>> @@ -66,6 +67,7 @@ struct fwnode_reference_args {
>> * endpoint node.
>> * @graph_get_port_parent: Return the parent node of a port node.
>> * @graph_parse_endpoint: Parse endpoint for port and endpoint id.
>> + * @get_match_data: Return the driver match data.
>
> Could you arrange the new get_match_data op closer to the other ops that
> don't deal with the graphs? Such as device_is_available. As the ops are
> dealing generally with fwnodes, I might call this device_get_match_data to
> explicitly mention it's for devices.
done
>
>> */
>> struct fwnode_operations {
>> void (*get)(struct fwnode_handle *fwnode);
>> @@ -101,6 +103,8 @@ struct fwnode_operations {
>> (*graph_get_port_parent)(struct fwnode_handle *fwnode);
>> int (*graph_parse_endpoint)(const struct fwnode_handle *fwnode,
>> struct fwnode_endpoint *endpoint);
>> + void *(*get_match_data)(const struct fwnode_handle *fwnode,
>> + struct device *dev);
>
> Same comment about the order here.
ok
>
>> };
>>
>> #define fwnode_has_op(fwnode, op) \
>> diff --git a/include/linux/property.h b/include/linux/property.h
>> index 6bebee1..01fa55b 100644
>> --- a/include/linux/property.h
>> +++ b/include/linux/property.h
>> @@ -275,6 +275,8 @@ int device_add_properties(struct device *dev,
>>
>> enum dev_dma_attr device_get_dma_attr(struct device *dev);
>>
>> +void *device_get_match_data(struct device *dev);
>> +
>> int device_get_phy_mode(struct device *dev);
>>
>> void *device_get_mac_address(struct device *dev, char *addr, int alen);
>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-12-07 20:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 17:04 [PATCH V6 0/7] dmaengine: qcom_hidma: add support for bugfixed HW Sinan Kaya
[not found] ` <1512493493-6464-1-git-send-email-okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-12-05 17:04 ` [PATCH V6 1/7] Documentation: DT: qcom_hidma: Bump HW revision for the " Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 2/7] ACPI / bus: Introduce acpi_get_match_data() function Sinan Kaya
2017-12-05 22:04 ` Rafael J. Wysocki
2017-12-06 16:41 ` Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 3/7] device property: Introduce a common API to fetch device match data Sinan Kaya
2017-12-07 12:29 ` Sakari Ailus
2017-12-07 20:15 ` Sinan Kaya [this message]
2017-12-07 12:40 ` Sakari Ailus
2017-12-07 20:17 ` Sinan Kaya
2017-12-07 22:06 ` Sakari Ailus
2017-12-07 22:19 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0inHMCLGyPaAeuJNo2VH7f3Th0KdpT2UkPBCsvrSDi0gQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-14 10:28 ` Sakari Ailus
2017-12-05 17:04 ` [PATCH V6 4/7] OF: properties: Implement get_match_data() callback Sinan Kaya
2017-12-05 21:21 ` Rob Herring
2017-12-07 12:38 ` Sakari Ailus
2017-12-07 13:10 ` Lothar Waßmann
2017-12-07 14:45 ` Sinan Kaya
[not found] ` <def8e351-bc2d-7adc-fdc5-362b365302a8-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-12-07 15:20 ` Lothar Waßmann
2017-12-07 17:50 ` Sinan Kaya
2017-12-08 8:09 ` Lothar Waßmann
2017-12-08 9:11 ` Lothar Waßmann
2017-12-08 14:33 ` Sinan Kaya
2017-12-08 14:40 ` Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 5/7] ACPI: " Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 6/7] dmaengine: qcom_hidma: Add support for the new revision Sinan Kaya
2017-12-05 17:04 ` [PATCH V6 7/7] dmaengine: qcom_hidma: Add identity register support Sinan Kaya
2017-12-05 22:05 ` [PATCH V6 0/7] dmaengine: qcom_hidma: add support for bugfixed HW Rafael J. Wysocki
2017-12-07 12:41 ` 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=74f88482-71ff-db72-ee6e-cc9b3b0bc37e@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=timur@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).