All of lore.kernel.org
 help / color / mirror / Atom feed
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-v3 2/3] mfd: 88pm800: Allow configuration of interrupt clear method
Date: Thu, 25 Jun 2015 14:32:34 +0900	[thread overview]
Message-ID: <558B9272.6090100@samsung.com> (raw)
In-Reply-To: <558B90F7.80700@linaro.org>

On 25.06.2015 14:26, Vaibhav Hiremath wrote:
> 
> 
> On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
>> 2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
>> <vaibhav.hiremath@linaro.org>:
>>> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
>>> (page 0) controls the method of clearing interrupt
>>> status of 88pm800 family of devices;
>>>
>>>    0: clear on read
>>>    1: clear on write
>>>
>>> This patch allows to configure this field, through DT.
>>>
>>> Also, as suggested by "Lee Jones" renaming DT property and variable
>>> field to appropriate name.
>>>
>>> Signed-off-by: Zhao Ye <zhaoy@marvell.com>
>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>>
>> It does not look like a property of the board. Instead it looks like a
>> runtime configuration so it should not be part of DT bindings.
>>
> 
> Why do you say that?
> 
> It is very well feature of 88PM860 device, where you can control irq
> clear operation (either read/write).
> 
> 
> Thanks,
> Vaibhav
> 
>> I understand that previously this was configured by platform data and
>> now you want to move everything to DT. But this does not belong to
>> DT...
>>
> 
> Thats not completely true.
> I think DT is the right place for this configuration.

DT and its bindings describe the specific board or device. Let me quote:
<<The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
structure and language for describing hardware.  More specifically, it
is a description of hardware that is readable by an operating system...>>

Whether you clear interrupts by writing or reading is configured during
runtime and it is completely independent to wiring. Each board with
88pm800 would allow both methods. So this is not a property of hardware
in the terms of open firmware. This is a runtime configuration.

Description of hardware would be a property which specifies whether a
88pm800-like device or a board using 88pm800 device ALLOWS choosing
different interrupt clearing.

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Vaibhav Hiremath
	<vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Zhao Ye <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH-v3 2/3] mfd: 88pm800: Allow configuration of interrupt clear method
Date: Thu, 25 Jun 2015 14:32:34 +0900	[thread overview]
Message-ID: <558B9272.6090100@samsung.com> (raw)
In-Reply-To: <558B90F7.80700-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>

On 25.06.2015 14:26, Vaibhav Hiremath wrote:
> 
> 
> On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
>> 2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
>> <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>:
>>> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
>>> (page 0) controls the method of clearing interrupt
>>> status of 88pm800 family of devices;
>>>
>>>    0: clear on read
>>>    1: clear on write
>>>
>>> This patch allows to configure this field, through DT.
>>>
>>> Also, as suggested by "Lee Jones" renaming DT property and variable
>>> field to appropriate name.
>>>
>>> Signed-off-by: Zhao Ye <zhaoy-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>>
>> It does not look like a property of the board. Instead it looks like a
>> runtime configuration so it should not be part of DT bindings.
>>
> 
> Why do you say that?
> 
> It is very well feature of 88PM860 device, where you can control irq
> clear operation (either read/write).
> 
> 
> Thanks,
> Vaibhav
> 
>> I understand that previously this was configured by platform data and
>> now you want to move everything to DT. But this does not belong to
>> DT...
>>
> 
> Thats not completely true.
> I think DT is the right place for this configuration.

DT and its bindings describe the specific board or device. Let me quote:
<<The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
structure and language for describing hardware.  More specifically, it
is a description of hardware that is readable by an operating system...>>

Whether you clear interrupts by writing or reading is configured during
runtime and it is completely independent to wiring. Each board with
88pm800 would allow both methods. So this is not a property of hardware
in the terms of open firmware. This is a runtime configuration.

Description of hardware would be a property which specifies whether a
88pm800-like device or a board using 88pm800 device ALLOWS choosing
different interrupt clearing.

Best regards,
Krzysztof


--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, Zhao Ye <zhaoy@marvell.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, lee.jones@linaro.org
Subject: Re: [PATCH-v3 2/3] mfd: 88pm800: Allow configuration of interrupt clear method
Date: Thu, 25 Jun 2015 14:32:34 +0900	[thread overview]
Message-ID: <558B9272.6090100@samsung.com> (raw)
In-Reply-To: <558B90F7.80700@linaro.org>

On 25.06.2015 14:26, Vaibhav Hiremath wrote:
> 
> 
> On Thursday 25 June 2015 05:33 AM, Krzysztof Kozlowski wrote:
>> 2015-06-24 18:21 GMT+09:00 Vaibhav Hiremath
>> <vaibhav.hiremath@linaro.org>:
>>> As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
>>> (page 0) controls the method of clearing interrupt
>>> status of 88pm800 family of devices;
>>>
>>>    0: clear on read
>>>    1: clear on write
>>>
>>> This patch allows to configure this field, through DT.
>>>
>>> Also, as suggested by "Lee Jones" renaming DT property and variable
>>> field to appropriate name.
>>>
>>> Signed-off-by: Zhao Ye <zhaoy@marvell.com>
>>> Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
>>
>> It does not look like a property of the board. Instead it looks like a
>> runtime configuration so it should not be part of DT bindings.
>>
> 
> Why do you say that?
> 
> It is very well feature of 88PM860 device, where you can control irq
> clear operation (either read/write).
> 
> 
> Thanks,
> Vaibhav
> 
>> I understand that previously this was configured by platform data and
>> now you want to move everything to DT. But this does not belong to
>> DT...
>>
> 
> Thats not completely true.
> I think DT is the right place for this configuration.

DT and its bindings describe the specific board or device. Let me quote:
<<The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
structure and language for describing hardware.  More specifically, it
is a description of hardware that is readable by an operating system...>>

Whether you clear interrupts by writing or reading is configured during
runtime and it is completely independent to wiring. Each board with
88pm800 would allow both methods. So this is not a property of hardware
in the terms of open firmware. This is a runtime configuration.

Description of hardware would be a property which specifies whether a
88pm800-like device or a board using 88pm800 device ALLOWS choosing
different interrupt clearing.

Best regards,
Krzysztof



  reply	other threads:[~2015-06-25  5:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  9:21 [PATCH-v3 0/3] mfd: 88pm800: Add Device tree support Vaibhav Hiremath
2015-06-24  9:21 ` Vaibhav Hiremath
2015-06-24  9:21 ` [PATCH-v3 1/3] mfd: 88pm800: Add device " Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath
2015-06-24 23:57   ` Krzysztof Kozlowski
2015-06-24 23:57     ` Krzysztof Kozlowski
2015-06-25  5:27     ` Vaibhav Hiremath
2015-06-25  5:27       ` Vaibhav Hiremath
2015-06-25  5:27       ` Vaibhav Hiremath
2015-06-25  5:37       ` Krzysztof Kozlowski
2015-06-25  5:37         ` Krzysztof Kozlowski
2015-06-24  9:21 ` [PATCH-v3 2/3] mfd: 88pm800: Allow configuration of interrupt clear method Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath
2015-06-25  0:03   ` Krzysztof Kozlowski
2015-06-25  0:03     ` Krzysztof Kozlowski
2015-06-25  0:03     ` Krzysztof Kozlowski
2015-06-25  5:26     ` Vaibhav Hiremath
2015-06-25  5:26       ` Vaibhav Hiremath
2015-06-25  5:32       ` Krzysztof Kozlowski [this message]
2015-06-25  5:32         ` Krzysztof Kozlowski
2015-06-25  5:32         ` Krzysztof Kozlowski
2015-06-25  5:44         ` Vaibhav Hiremath
2015-06-25  5:44           ` Vaibhav Hiremath
2015-06-25  5:50           ` Krzysztof Kozlowski
2015-06-25  5:50             ` Krzysztof Kozlowski
2015-06-25  5:50             ` Krzysztof Kozlowski
2015-06-25  5:57             ` Vaibhav Hiremath
2015-06-25  5:57               ` Vaibhav Hiremath
2015-06-25  5:57               ` Vaibhav Hiremath
2015-06-25  6:05               ` Krzysztof Kozlowski
2015-06-25  6:05                 ` Krzysztof Kozlowski
2015-06-24  9:21 ` [PATCH-v3 3/3] mfd: devicetree: bindings: Add new 88pm800 mfd binding Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath
2015-06-24  9:21   ` Vaibhav Hiremath

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=558B9272.6090100@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.