xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Goel, Sameer" <sgoel@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: Tomasz Nowicki <tn@semihalf.com>,
	Punit Agrawal <punit.agrawal@arm.com>,
	xen-devel@lists.xenproject.org, 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: Mon, 28 Aug 2017 15:42:46 -0600	[thread overview]
Message-ID: <ddb5c468-e0fe-bc7c-8391-fbe79bbaa5ae@codeaurora.org> (raw)
In-Reply-To: <54e9dbf7-8e48-8d0b-2290-fd2a4eb07e8c@arm.com>



On 6/12/2017 6:40 AM, Julien Grall wrote:
> Hi,
> 
> On 08/06/17 22:57, Stefano Stabellini wrote:
>> On Thu, 8 Jun 2017, Goel, Sameer wrote:
>>>>> 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?
>>
>> Usually we keep the imported Linux definitions as-is.
> 
> If we keep as-is, the coding style should stay exactly the same. Even
> 
> Otherwise there is no point to import a verbatim copy of Linux as it would be difficult to keep track of the changes.
> 
> In this case, I am not convinced we have a benefits to keep this code close to Linux. It is small enough and we don't need 80% of it.
Ok. I will go ahead and remove whatever is not needed.
> 
> Cheers,
> 

-- 
 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

  reply	other threads:[~2017-08-28 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
2017-06-08 21:57       ` Stefano Stabellini
2017-06-12 12:40         ` Julien Grall
2017-08-28 21:42           ` Goel, Sameer [this message]
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=ddb5c468-e0fe-bc7c-8391-fbe79bbaa5ae@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).