All of lore.kernel.org
 help / color / mirror / Atom feed
From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
	lenb@kernel.org, catalin.marinas@arm.com, will.deacon@arm.com,
	thomas.lendacky@amd.com, herbert@gondor.apana.org.au,
	davem@davemloft.net, arnd@arndb.de, msalter@redhat.com,
	hanjun.guo@linaro.org, al.stone@linaro.org,
	grant.likely@linaro.org, leo.duran@amd.com,
	linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org,
	netdev@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [V3 PATCH 3/5] device property: Introduces device_dma_is_coherent()
Date: Fri, 08 May 2015 13:36:06 -0700	[thread overview]
Message-ID: <554D1E36.1030607@oracle.com> (raw)
In-Reply-To: <6693356.eSISHsdLqF@vostro.rjw.lan>

On 5/8/2015 1:58 PM, Rafael J. Wysocki wrote:
> On Friday, May 08, 2015 01:27:00 PM santosh shilimkar wrote:
>> On 5/8/2015 1:49 PM, Rafael J. Wysocki wrote:
>>> On Thursday, May 07, 2015 09:12:00 PM santosh.shilimkar@oracle.com wrote:
>>>> On 5/7/15 5:37 PM, Suravee Suthikulpanit wrote:
>>>>> Currently, device drivers, which support both OF and ACPI,
>>>>> need to call two separate APIs, of_dma_is_coherent() and
>>>>> acpi_dma_is_coherent()) to determine device coherency attribute.
>>>>>
>>>>> This patch simplifies this process by introducing a new device
>>>>> property API, device_dma_is_coherent(), which calls the appropriate
>>>>> interface based on the booting architecture.
>>>>>
>>>>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>>> ---
>>>>>     drivers/base/property.c  | 12 ++++++++++++
>>>>>     include/linux/property.h |  2 ++
>>>>>     2 files changed, 14 insertions(+)
>>>>>
>>>>> diff --git a/drivers/base/property.c b/drivers/base/property.c
>>>>> index 1d0b116..8123c6e 100644
>>>>> --- a/drivers/base/property.c
>>>>> +++ b/drivers/base/property.c
>>>>> @@ -14,6 +14,7 @@
>>>>>     #include <linux/export.h>
>>>>>     #include <linux/kernel.h>
>>>>>     #include <linux/of.h>
>>>>> +#include <linux/of_address.h>
>>>>>     #include <linux/property.h>
>>>>>
>>>>>     /**
>>>>> @@ -519,3 +520,14 @@ unsigned int device_get_child_node_count(struct device *dev)
>>>>>     	return count;
>>>>>     }
>>>>>     EXPORT_SYMBOL_GPL(device_get_child_node_count);
>>>>> +
>>>>> +bool device_dma_is_coherent(struct device *dev)
>>>>> +{
>>>>> +	if (IS_ENABLED(CONFIG_OF) && dev->of_node)
>>>>
>>>> Do you really need that IS_ENABLED(CONFIG_OF) ?
>>>> In other words, dev->of_node should be null for !CONFIG_OF
>>>
>>> Yes, but IS_ENABLED(CONFIG_OF) causes the check to be optimized away by the
>>> compiler if CONFIG_OF is not enabled.
>>>
>> Sure but my point was why you need it when just 'dev->of_node' check
>> is enough. May be I missed something.
>
> dev->of_node is present when CONFIG_OF is not enabled too.  Without the
> IS_ENABLED(CONFIG_OF) this becomes a pointless pointer check that will
> always evaluate to 'false' on systems without CONFIG_OF, AFAICS.
>
Got it now. Thanks for expanding it.

Regards,
Santosh

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [V3 PATCH 3/5] device property: Introduces device_dma_is_coherent()
Date: Fri, 08 May 2015 13:36:06 -0700	[thread overview]
Message-ID: <554D1E36.1030607@oracle.com> (raw)
In-Reply-To: <6693356.eSISHsdLqF@vostro.rjw.lan>

On 5/8/2015 1:58 PM, Rafael J. Wysocki wrote:
> On Friday, May 08, 2015 01:27:00 PM santosh shilimkar wrote:
>> On 5/8/2015 1:49 PM, Rafael J. Wysocki wrote:
>>> On Thursday, May 07, 2015 09:12:00 PM santosh.shilimkar at oracle.com wrote:
>>>> On 5/7/15 5:37 PM, Suravee Suthikulpanit wrote:
>>>>> Currently, device drivers, which support both OF and ACPI,
>>>>> need to call two separate APIs, of_dma_is_coherent() and
>>>>> acpi_dma_is_coherent()) to determine device coherency attribute.
>>>>>
>>>>> This patch simplifies this process by introducing a new device
>>>>> property API, device_dma_is_coherent(), which calls the appropriate
>>>>> interface based on the booting architecture.
>>>>>
>>>>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
>>>>> ---
>>>>>     drivers/base/property.c  | 12 ++++++++++++
>>>>>     include/linux/property.h |  2 ++
>>>>>     2 files changed, 14 insertions(+)
>>>>>
>>>>> diff --git a/drivers/base/property.c b/drivers/base/property.c
>>>>> index 1d0b116..8123c6e 100644
>>>>> --- a/drivers/base/property.c
>>>>> +++ b/drivers/base/property.c
>>>>> @@ -14,6 +14,7 @@
>>>>>     #include <linux/export.h>
>>>>>     #include <linux/kernel.h>
>>>>>     #include <linux/of.h>
>>>>> +#include <linux/of_address.h>
>>>>>     #include <linux/property.h>
>>>>>
>>>>>     /**
>>>>> @@ -519,3 +520,14 @@ unsigned int device_get_child_node_count(struct device *dev)
>>>>>     	return count;
>>>>>     }
>>>>>     EXPORT_SYMBOL_GPL(device_get_child_node_count);
>>>>> +
>>>>> +bool device_dma_is_coherent(struct device *dev)
>>>>> +{
>>>>> +	if (IS_ENABLED(CONFIG_OF) && dev->of_node)
>>>>
>>>> Do you really need that IS_ENABLED(CONFIG_OF) ?
>>>> In other words, dev->of_node should be null for !CONFIG_OF
>>>
>>> Yes, but IS_ENABLED(CONFIG_OF) causes the check to be optimized away by the
>>> compiler if CONFIG_OF is not enabled.
>>>
>> Sure but my point was why you need it when just 'dev->of_node' check
>> is enough. May be I missed something.
>
> dev->of_node is present when CONFIG_OF is not enabled too.  Without the
> IS_ENABLED(CONFIG_OF) this becomes a pointless pointer check that will
> always evaluate to 'false' on systems without CONFIG_OF, AFAICS.
>
Got it now. Thanks for expanding it.

Regards,
Santosh

  reply	other threads:[~2015-05-08 20:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  0:37 [V3 PATCH 0/5] ACPI: Introduce support for _CCA object Suravee Suthikulpanit
2015-05-08  0:37 ` Suravee Suthikulpanit
2015-05-08  0:37 ` Suravee Suthikulpanit
2015-05-08  0:37 ` [V3 PATCH 1/5] ACPI / scan: Parse _CCA and setup device coherency Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08 20:53   ` Rafael J. Wysocki
2015-05-08 20:53     ` Rafael J. Wysocki
2015-05-11 16:16     ` Catalin Marinas
2015-05-11 16:16       ` Catalin Marinas
2015-05-12  1:20       ` Rafael J. Wysocki
2015-05-12  1:20         ` Rafael J. Wysocki
2015-05-12 15:06         ` Suravee Suthikulanit
2015-05-12 15:06           ` Suravee Suthikulanit
2015-05-12 15:06           ` Suravee Suthikulanit
2015-05-08  0:37 ` [V3 PATCH 2/5] arm64 : Introduce support for ACPI _CCA object Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08 20:55   ` Rafael J. Wysocki
2015-05-08 20:55     ` Rafael J. Wysocki
2015-05-11 17:12   ` Catalin Marinas
2015-05-11 17:12     ` Catalin Marinas
2015-05-08  0:37 ` [V3 PATCH 3/5] device property: Introduces device_dma_is_coherent() Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  4:12   ` santosh.shilimkar
2015-05-08  4:12     ` santosh.shilimkar at oracle.com
2015-05-08 20:49     ` Rafael J. Wysocki
2015-05-08 20:49       ` Rafael J. Wysocki
2015-05-08 20:27       ` santosh shilimkar
2015-05-08 20:27         ` santosh shilimkar
2015-05-08 20:58         ` Rafael J. Wysocki
2015-05-08 20:58           ` Rafael J. Wysocki
2015-05-08 20:36           ` santosh shilimkar [this message]
2015-05-08 20:36             ` santosh shilimkar
2015-05-08  0:37 ` [V3 PATCH 4/5] crypto: ccp - Unify coherency checking logic with device_dma_is_coherent() Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37 ` [V3 PATCH 5/5] amd-xgbe: " Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit
2015-05-08  0:37   ` Suravee Suthikulpanit

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=554D1E36.1030607@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=al.stone@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=davem@davemloft.net \
    --cc=grant.likely@linaro.org \
    --cc=hanjun.guo@linaro.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=lenb@kernel.org \
    --cc=leo.duran@amd.com \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=thomas.lendacky@amd.com \
    --cc=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.