lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 20 May 2017 07:43:15 +0100
From:   Marc Zyngier <marc.zyngier@....com>
To:     Matthias Brugger <matthias.bgg@...il.com>
Cc:     laurentiu.tudor@....com, gregkh@...uxfoundation.org,
        stuyoder@...il.com, devel@...verdev.osuosl.org, arnd@...db.de,
        ruxandra.radulescu@....com, Stuart Yoder <stuart.yoder@....com>,
        roy.pledge@....com, linux-kernel@...r.kernel.org, agraf@...e.de,
        catalin.horghidan@....com, ioana.ciornei@....com,
        Thomas Gleixner <tglx@...utronix.de>, leoyang.li@....com,
        bharat.bhushan@....com, Jason Cooper <jason@...edaemon.net>,
        linux-arm-kernel@...ts.infradead.org,
        Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 3/3][v4] staging: fsl-mc: move bus driver out of staging

On Fri, May 19 2017 at 02:41:43 PM, Matthias Brugger <matthias.bgg@...il.com> wrote:
> On 19/05/17 15:13, laurentiu.tudor@....com wrote:
>> From: Stuart Yoder <stuart.yoder@....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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ