From: b-cousson@ti•com (Cousson, Benoit)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv2 3/3] arm: dts: add bandgap entry for OMAP4460 devices
Date: Wed, 29 May 2013 16:19:42 +0200 [thread overview]
Message-ID: <51A60E7E.2070905@ti.com> (raw)
In-Reply-To: <51A60C74.4010307@ti.com>
Hi Eduardo,
On 5/29/2013 4:11 PM, Eduardo Valentin wrote:
> Salut Monsieur Benoit,
>
> On 16-05-2013 08:27, Eduardo Valentin wrote:
>> On 16-05-2013 03:20, Benoit Cousson wrote:
>>> Hi Eduardo,
>>>
>
> <cut>
>
>>> We need to check.
>>
>> Yeah, I also dont think this will work, because we will reparent the
>> interrupt, setting to a different controller. That will break the TALERT
>> signal already defined at GIC (check original patch).
>>
>> I propose keeping the way I sent. Unless there is a way to set two
>> different controllers to same device.
>>
>
> Any idea on this patch? Shall we keep the way it is?
Well since we cannot use directly interrupt, I think we need to use at
least the proper gpio binding.
Thanks,
Benoit
next prev parent reply other threads:[~2013-05-29 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1368629928-6723-1-git-send-email-eduardo.valentin@ti.com>
2013-05-15 14:58 ` [PATCHv2 1/3] arm: introduce config HAS_BANDGAP Eduardo Valentin
2013-05-31 15:03 ` Eduardo Valentin
2013-05-31 15:12 ` Fabio Estevam
2013-06-04 12:32 ` Eduardo Valentin
2013-06-04 12:42 ` [PATCHv3 " Eduardo Valentin
2013-05-15 14:58 ` [PATCHv2 2/3] arm: dts: add bandgap entry for OMAP443x devices Eduardo Valentin
2013-05-15 14:58 ` [PATCHv2 3/3] arm: dts: add bandgap entry for OMAP4460 devices Eduardo Valentin
2013-05-15 15:23 ` Benoit Cousson
2013-05-15 16:36 ` Eduardo Valentin
2013-05-15 16:57 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-16 12:29 ` Eduardo Valentin
2013-05-31 15:24 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-16 7:20 ` Benoit Cousson
2013-05-16 12:27 ` Eduardo Valentin
2013-05-29 14:11 ` Eduardo Valentin
2013-05-29 14:19 ` Cousson, Benoit [this message]
2013-05-29 15:42 ` Eduardo Valentin
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=51A60E7E.2070905@ti.com \
--to=b-cousson@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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