Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: GICv3: Support for active low level-sensitive PPIs in device-tree binding
Date: Fri, 27 Feb 2015 11:26:23 +0000	[thread overview]
Message-ID: <20150227112623.57915b1f@arm.com> (raw)
In-Reply-To: <BY1PR0301MB1303EF578091444B2C5CA3AD82150@BY1PR0301MB1303.namprd03.prod.outlook.com>

On Fri, 27 Feb 2015 11:13:08 +0000
"bhupesh.sharma at freescale.com" <bhupesh.sharma@freescale.com> wrote:

> Hi,
> 
> While the GICv2 device-tree binding document (see [1]) seems to have
> support for active low level-sensitive PPIs:
> 
> The 3rd cell is the flags, encoded as follows:
> 	bits[3:0] trigger type and level flags.
> 		1 = low-to-high edge triggered
> 		2 = high-to-low edge triggered (invalid for SPIs)
> 		4 = active high level-sensitive
> 		8 = active low level-sensitive (invalid for SPIs).
> 
> The GICv3 device-tree bindings (see [2]) on the other hand, seem to
> be lacking the same for active low level-sensitive PPIs:
> 
>   The 3rd cell is the flags, encoded as follows:
> 	bits[3:0] trigger type and level flags.
> 		1 = edge triggered
> 		4 = level triggered
> 
> One of our SoC, supports active low level-sensitive PPIs on GICv3. If
> I spin-out a patch to address the same in GICv3 bindings, will that
> be acceptable, or, is something on similar lines already in-work.

Yes, please send in a patch (possible saying "valid for PPIs only"
instead of "invalid for SPIs", so that we don't have to restrict it
for LPIs either).

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny.

  reply	other threads:[~2015-02-27 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 11:13 GICv3: Support for active low level-sensitive PPIs in device-tree binding bhupesh.sharma at freescale.com
2015-02-27 11:26 ` Marc Zyngier [this message]
2015-02-27 11:30   ` bhupesh.sharma at freescale.com

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=20150227112623.57915b1f@arm.com \
    --to=marc.zyngier@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox