linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: "'Lee Jones'" <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, arnd@arndb.de,
	b29396@freescale.com, boris.brezillon@free-electrons.com,
	tomasz.figa@gmail.com, linux@arm.linux.org.uk,
	vikas.sajjan@samsung.com, naushad@samsung.com,
	thomas.ab@samsung.com, kgene.kim@samsung.com,
	Li.Xiubo@freescale.com, geert+renesas@glider.be,
	swarren@nvidia.com
Subject: RE: [PATCH v7] mfd: syscon: Decouple syscon interface from platform devices
Date: Wed, 22 Oct 2014 16:36:28 +0530	[thread overview]
Message-ID: <001901cfede8$5554cc50$fffe64f0$@samsung.com> (raw)
In-Reply-To: <20141007090923.GI25331@lee--X1>

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@arndb.de>
> > Suggested-by: Tomasz Figa <tomasz.figa@gmail.com>
> > Tested-by: Vivek Gautam <gautam.vivek@samsung.com>
> > Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> > Tested-by: Heiko Stuebner <heiko@sntech.de>
> > Reviewed-by: Heiko Stuebner <heiko@sntech.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


  reply	other threads:[~2014-10-22 11:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30  8:35 [PATCH v7] mfd: syscon: Decouple syscon interface from platform devices Pankaj Dubey
2014-09-30 16:09 ` Doug Anderson
2014-10-06  9:02   ` Pankaj Dubey
2014-10-06 16:27     ` Lee Jones
2014-10-07  9:09 ` Lee Jones
2014-10-22 11:06   ` Pankaj Dubey [this message]
2014-10-22 12:12     ` Lee Jones

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='001901cfede8$5554cc50$fffe64f0$@samsung.com' \
    --to=pankaj.dubey@samsung.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=arnd@arndb.de \
    --cc=b29396@freescale.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=geert+renesas@glider.be \
    --cc=kgene.kim@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=naushad@samsung.com \
    --cc=swarren@nvidia.com \
    --cc=thomas.ab@samsung.com \
    --cc=tomasz.figa@gmail.com \
    --cc=vikas.sajjan@samsung.com \
    /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).