From: "Goel, Sameer" <sgoel@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Tomasz Nowicki <tn@semihalf.com>,
Punit Agrawal <punit.agrawal@arm.com>,
nd@arm.com, Robin Murphy <robin.murphy@arm.com>,
Shanker Donthineni <shankerd@codeaurora.org>
Subject: Re: [RFC 2/6] arm64: Add definitions for fwnode_handle
Date: Thu, 8 Jun 2017 15:42:51 -0600 [thread overview]
Message-ID: <59a46595-2660-8dfa-48b5-5424c31c842f@codeaurora.org> (raw)
In-Reply-To: <2b498c6b-46cd-d264-819c-b3eb62cc7ef3@arm.com>
On 6/8/2017 1:59 PM, Julien Grall wrote:
>
>
> On 08/06/2017 20:30, Sameer Goel wrote:
>> This will be used as a device property to match the DMA capable devices
>> with the associated SMMU. The header file is a port from linux.
>>
>> Linux ChangeId:ce793486e23e: driver core / ACPI: Represent ACPI
>> companions using fwnode_handle
>>
>> Signed-off-by: Sameer Goel <sgoel@codeaurora.org>
>> ---
>> xen/include/asm-arm/device.h | 2 ++
>> xen/include/xen/fwnode.h | 35 +++++++++++++++++++++++++++++++++++
>> 2 files changed, 37 insertions(+)
>> create mode 100644 xen/include/xen/fwnode.h
>>
>> diff --git a/xen/include/asm-arm/device.h b/xen/include/asm-arm/device.h
>> index 6734ae8..78c38fe 100644
>> --- a/xen/include/asm-arm/device.h
>> +++ b/xen/include/asm-arm/device.h
>> @@ -2,6 +2,7 @@
>> #define __ASM_ARM_DEVICE_H
>>
>> #include <xen/init.h>
>> +#include <xen/fwnode.h>
>>
>> enum device_type
>> {
>> @@ -19,6 +20,7 @@ struct device
>> #ifdef CONFIG_HAS_DEVICE_TREE
>> struct dt_device_node *of_node; /* Used by drivers imported from Linux */
>> #endif
>> + struct fwnode_handle *fwnode; /*fw device node identifier */
>
> I am a bit surprised you don't rework struct dev. As of_node is now redundant with fwnode.
I agree that this will eventually be removed. I have kept this in now just to maintain compatibility
(compilation and otherwise) with smmuv2 driver. I will add a comment to indicate this. So that it can
be easily identified and remove when we do a final cleanup. Can I prefix the comment with with XEN:TODO:?
>
>> struct dev_archdata archdata;
>> };
>>
>> diff --git a/xen/include/xen/fwnode.h b/xen/include/xen/fwnode.h
>> new file mode 100644
>> index 0000000..db65b15
>> --- /dev/null
>> +++ b/xen/include/xen/fwnode.h
>> @@ -0,0 +1,35 @@
>> +/*
>> + * fwnode.h - Firmware device node object handle type definition.
>> + *
>> + * Copyright (C) 2015, Intel Corporation
>> + * Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + *
>> + * Ported from Linux include/linux/fwnode.h
>> + * => commit ce793486e23e0162a732c605189c8028e0910e86
>> + *
>> + * No functional Xen modifications.
>> + */
>> +
>> +#ifndef __XEN_FWNODE_H_
>> +#define __XEN_FWNODE_H_
>> +
>> +enum fwnode_type {
>> + FWNODE_INVALID = 0,
>> + FWNODE_OF,
>> + FWNODE_ACPI,
>> + FWNODE_ACPI_DATA,
>> + FWNODE_ACPI_STATIC,
>> + FWNODE_PDATA,
>> + FWNODE_IRQCHIP
>
> Do you really need to introduce all of them?
>
Not really. We are interested in OF and ACPI_STATIC for now. Since the verbatim file from Linux applied ok, I did not remove the other entries.
What's your recommendation?
>> +};
>> +
>> +struct fwnode_handle {
>> + enum fwnode_type type;
>> + struct fwnode_handle *secondary;
>> +};
>> +
>> +#endif
>>
>
> Cheers,
>
Thanks,
Sameer
--
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-08 21:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 19:30 [RFC 0/6] IORT support and introduce fwspec Sameer Goel
2017-06-08 19:30 ` [RFC 1/6] passthrough/arm: Modify SMMU driver to use generic device definition Sameer Goel
2017-06-12 12:34 ` Julien Grall
2017-06-08 19:30 ` [RFC 2/6] arm64: Add definitions for fwnode_handle Sameer Goel
2017-06-08 19:47 ` Julien Grall
2017-06-08 19:59 ` Julien Grall
2017-06-08 21:42 ` Goel, Sameer [this message]
2017-06-08 21:57 ` Stefano Stabellini
2017-06-12 12:40 ` Julien Grall
2017-08-28 21:42 ` Goel, Sameer
2017-06-12 12:51 ` Julien Grall
2017-08-28 21:41 ` Goel, Sameer
2017-06-08 19:30 ` [RFC 3/6] Introduce _xrealloc Sameer Goel
2017-06-08 19:49 ` Julien Grall
2017-06-09 9:44 ` Wei Liu
2017-08-28 21:39 ` Goel, Sameer
2017-10-12 13:33 ` Julien Grall
2017-10-12 14:45 ` Wei Liu
2017-06-08 21:51 ` Stefano Stabellini
2017-06-08 19:30 ` [RFC 4/6] xen/passthrough/arm: Introduce iommu_fwspec Sameer Goel
2017-06-08 20:02 ` Julien Grall
2017-06-08 19:30 ` [RFC 5/6] ACPI: arm: Support for IORT Sameer Goel
2017-07-14 15:36 ` Jan Beulich
2017-06-08 19:30 ` [RFC 6/6] acpi:arm64: Add support for parsing IORT table Sameer Goel
2017-06-08 22:22 ` Stefano Stabellini
2017-06-09 11:15 ` Robin Murphy
2017-06-12 13:36 ` Julien Grall
2017-06-12 13:44 ` Jan Beulich
2017-06-21 16:55 ` Robin Murphy
2017-08-28 21:48 ` Goel, Sameer
2017-06-12 13:24 ` Julien Grall
2017-08-28 22:21 ` Goel, Sameer
2017-09-12 11:25 ` Julien Grall
2017-09-21 0:37 ` Goel, Sameer
2017-09-21 10:54 ` Julien Grall
2017-07-14 15:41 ` Jan Beulich
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=59a46595-2660-8dfa-48b5-5424c31c842f@codeaurora.org \
--to=sgoel@codeaurora.org \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=punit.agrawal@arm.com \
--cc=robin.murphy@arm.com \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=tn@semihalf.com \
--cc=xen-devel@lists.xenproject.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).