linux-kernel - RE: [PATCH v7] mfd: syscon: Decouple syscon interface from platform devices

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:	Wed, 22 Oct 2014 16:36:28 +0530
From:	Pankaj Dubey <pankaj.dubey@...sung.com>
To:	'Lee Jones' <lee.jones@...aro.org>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, arnd@...db.de,
	b29396@...escale.com, boris.brezillon@...e-electrons.com,
	tomasz.figa@...il.com, linux@....linux.org.uk,
	vikas.sajjan@...sung.com, naushad@...sung.com,
	thomas.ab@...sung.com, kgene.kim@...sung.com,
	Li.Xiubo@...escale.com, geert+renesas@...der.be, swarren@...dia.com
Subject: RE: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
 devices

Hello Lee,

On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
> On Tue, 30 Sep 2014, Pankaj Dubey wrote:
> 
> > Currently a syscon entity can be only registered directly through a
> > platform device that binds to a dedicated syscon driver. However in
> > certain use cases it is desirable to make a device used with another
> > driver a syscon interface provider.
> >
> > For example, certain SoCs (e.g. Exynos) contain system controller
> > blocks which perform various functions such as power domain control,
> > CPU power management, low power mode control, but in addition contain
> > certain IP integration glue, such as various signal masks, coprocessor
> > power control, etc. In such case, there is a need to have a dedicated
> > driver for such system controller but also share registers with other
> > drivers. The latter is where the syscon interface is helpful.
> >
> > In case of DT based platforms, this patch decouples syscon object from
> > syscon platform driver, and allows to create syscon objects first time
> > when it is required by calling of syscon_regmap_lookup_by APIs and
> > keep a list of such syscon objects along with syscon provider
> > device_nodes and regmap handles.
> >
> > For non-DT based platforms, this patch keeps syscon platform driver
> > structure so that syscon can be probed and such non-DT based drivers
> > can use syscon_regmap_lookup_by_pdev API and access regmap handles.
> > Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based,
> > we can completely remove platform driver of syscon, and keep only
> > helper functions to get regmap handles.
> >
> > Suggested-by: Arnd Bergmann <arnd@...db.de>
> > Suggested-by: Tomasz Figa <tomasz.figa@...il.com>
> > Tested-by: Vivek Gautam <gautam.vivek@...sung.com>
> > Tested-by: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
> > Signed-off-by: Pankaj Dubey <pankaj.dubey@...sung.com>
> > Reviewed-by: Arnd Bergmann <arnd@...db.de>
> > Tested-by: Heiko Stuebner <heiko@...ech.de>
> > Reviewed-by: Heiko Stuebner <heiko@...ech.de>
> 
> Applied for v3.19.

I can't see this in 3.18-rc1, as this patch is one of dependency for many of Exynos PMU related patches,
will you please queue this patch for 3.18-rc2, so that already ready to be in patches having this patch as
dependency can be taken in.

Thanks,
Pankaj Dubey
> 
> --
> Lee Jones
> Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software
> for ARM SoCs Follow Linaro: Facebook | Twitter | Blog

--
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/