[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57320597.hlx9GuXmaF@wuerfel>
Date: Wed, 03 Dec 2014 11:52:41 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Stefan Agner <stefan@...er.ch>, shawn.guo@...aro.org,
kernel@...gutronix.de, linux@....linux.org.uk,
u.kleine-koenig@...gutronix.de, jason@...edaemon.net,
olof@...om.net, daniel.lezcano@...aro.org, tglx@...utronix.de,
mark.rutland@....com, pawel.moll@....com, robh+dt@...nel.org,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/12] Documentation: dt: imx: add MSCM documentation
On Wednesday 03 December 2014 01:12:06 Stefan Agner wrote:
> +Freescale Vybrid Miscellaneous System Control Module
> +
> +The MSCM IP contains Access Control and TrustZone Security hardware,
> +CPU Configuration registers and Interrupt Router control.
> +
> +Required properties:
> +- compatible : "fsl,vf610-mscm"
> +- reg : the register range of the MSCM module
> +
> +Example:
> + mscm: mscm@...01000 {
> + compatible = "fsl,vf610-mscm";
> + reg = <0x40001000 0x1000>;
> + };
This sounds like one of those generic system controller devices.
Should this be marked as syscon an accessed through
syscon_regmap_lookup_by_phandle()?
If you only eve have one driver touching these registers, that
won't be necessary of course.
arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists