linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3][v4] staging: fsl-mc: move bus driver out of staging
Date: Sat, 20 May 2017 07:43:15 +0100	[thread overview]
Message-ID: <86tw4g6nb0.fsf@arm.com> (raw)
In-Reply-To: <b3980350-9663-d98b-6533-fd3c15f98671@gmail.com> (Matthias Brugger's message of "Fri, 19 May 2017 15:41:43 +0200")

On Fri, May 19 2017 at 02:41:43 PM, Matthias Brugger <matthias.bgg@gmail.com> wrote:
> On 19/05/17 15:13, laurentiu.tudor at nxp.com wrote:
>> From: Stuart Yoder <stuart.yoder@nxp.com>
>>
>> Move the source files out of staging into their final locations:
>>    -include files in drivers/staging/fsl-mc/include go to include/linux/fsl
>>    -irq-gic-v3-its-fsl-mc-msi.c goes to drivers/irqchip
>
> This driver has as compatible "arm,gic-v3-its". I wonder if this is
> correct and if it should be moved like this out of staging.

This is no different from the way we handle *any* bus that uses the
GICv3 ITS as an MSI controller. Each bus provides its glue code that
latches onto the ITS node, and calls into the generic code.

Now, when it comes to moving this out of staging, here is my concern:
There is mention of a userspace tool (restool) used to control the
HW. Where is this tool? Where is the user ABI documented?

Thanks,

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

  parent reply	other threads:[~2017-05-20  6:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 13:13 [PATCH 0/3][v4] staging: fsl-mc: move bus driver out of staging laurentiu.tudor at nxp.com
2017-05-19 13:13 ` [PATCH 1/3] staging: fsl-mc: fix several checkpath.pl warnings laurentiu.tudor at nxp.com
2017-05-19 13:13 ` [PATCH 2/3] staging: fsl-mc: add binding path to MAINTAINERS laurentiu.tudor at nxp.com
2017-05-19 13:13 ` [PATCH 3/3][v4] staging: fsl-mc: move bus driver out of staging laurentiu.tudor at nxp.com
2017-05-19 13:41   ` Matthias Brugger
2017-05-19 22:57     ` Stuart Yoder
2017-05-20  6:43     ` Marc Zyngier [this message]
2017-05-22  7:12       ` Laurentiu Tudor
2017-05-22  7:40         ` Marc Zyngier
2017-05-22  8:42           ` Laurentiu Tudor
2017-05-22  9:06             ` Marc Zyngier
2017-05-22  9:15               ` Laurentiu Tudor

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=86tw4g6nb0.fsf@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;
as well as URLs for NNTP newsgroup(s).