On Mon, Jan 6, 2014 at 6:36 AM, Michal Simek <[email protected]> wrote: > From: Steffen Trumtrar <[email protected]> > > For later usage by zynq clk driver. > > Signed-off-by: Steffen Trumtrar <[email protected]> > Signed-off-by: Michal Simek <[email protected]> > --- > arch/arm/mach-zynq/slcr.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm/mach-zynq/slcr.c b/arch/arm/mach-zynq/slcr.c > index 9746de7..2891dcf 100644 > --- a/arch/arm/mach-zynq/slcr.c > +++ b/arch/arm/mach-zynq/slcr.c > @@ -121,6 +121,8 @@ int __init zynq_early_slcr_init(void) > BUG(); > } > > + np->data = (__force void *)zynq_slcr_base;
This is quite unusual, we normally remap again if needed. Is there a reason you can't just have the driver request the resource and map it like most other ones do? -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
