From: Lee Jones <lee.jones@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pankaj Dubey <pankaj.dubey@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kgene.kim@samsung.com, linux@arm.linux.org.uk,
vikas.sajjan@samsung.com, joshi@samsung.com, naushad@samsung.com,
thomas.ab@samsung.com, chow.kim@samsung.com,
Tomasz Figa <t.figa@samsung.com>,
broonie@kernel.org
Subject: Re: [PATCH] mfd: syscon: Decouple syscon interface from syscon devices
Date: Mon, 1 Sep 2014 12:25:49 +0100 [thread overview]
Message-ID: <20140901112549.GM7374@lee--X1> (raw)
In-Reply-To: <4121644.3haxjiIdIo@wuerfel>
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
> On Monday 01 September 2014 08:49:18 Lee Jones wrote:
> > On Fri, 22 Aug 2014, Pankaj Dubey wrote:
> >
> > > From: Tomasz Figa <t.figa@samsung.com>
> > >
> > > Currently a syscon entity can be only registered directly through a
> > > platform device that binds to a dedicated 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.
> > >
> > > This patch decouples syscon object from syscon driver, so that it can be
> > > registered from any driver in addition to the original "syscon" platform
> > > driver.
> > >
> > > Signed-off-by: Tomasz Figa <t.figa@samsung.com>
> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > > ---
> > >
> > > RFC patch [1] was posted by Tomasz Figa. This patch addresses some of
> > > comments given by Arnd to RFC patch, and further decouples syscon from
> > > device model. It also gives flexibility of registering with syscon at
> > > early stage using device_node object.
> >
> > It would be helpful if Arnd gave this revision his blessing (Ack).
>
> I never saw a reason why we don't take this all the way as discussed
> a few times: Completely remove the dependency of syscon on having
> a platform driver for it, and make it possible to just call
> syscon_regmap_lookup_by_phandle() without having to register
> it first.
I think this sounds like a good end-state. Migrating over by
supporting both methods in this way does sound like the correct thing
to do though. Doing so is likely to dramatically reduce the effect on
current users.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mfd: syscon: Decouple syscon interface from syscon devices
Date: Mon, 1 Sep 2014 12:25:49 +0100 [thread overview]
Message-ID: <20140901112549.GM7374@lee--X1> (raw)
In-Reply-To: <4121644.3haxjiIdIo@wuerfel>
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
> On Monday 01 September 2014 08:49:18 Lee Jones wrote:
> > On Fri, 22 Aug 2014, Pankaj Dubey wrote:
> >
> > > From: Tomasz Figa <t.figa@samsung.com>
> > >
> > > Currently a syscon entity can be only registered directly through a
> > > platform device that binds to a dedicated 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.
> > >
> > > This patch decouples syscon object from syscon driver, so that it can be
> > > registered from any driver in addition to the original "syscon" platform
> > > driver.
> > >
> > > Signed-off-by: Tomasz Figa <t.figa@samsung.com>
> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > > ---
> > >
> > > RFC patch [1] was posted by Tomasz Figa. This patch addresses some of
> > > comments given by Arnd to RFC patch, and further decouples syscon from
> > > device model. It also gives flexibility of registering with syscon at
> > > early stage using device_node object.
> >
> > It would be helpful if Arnd gave this revision his blessing (Ack).
>
> I never saw a reason why we don't take this all the way as discussed
> a few times: Completely remove the dependency of syscon on having
> a platform driver for it, and make it possible to just call
> syscon_regmap_lookup_by_phandle() without having to register
> it first.
I think this sounds like a good end-state. Migrating over by
supporting both methods in this way does sound like the correct thing
to do though. Doing so is likely to dramatically reduce the effect on
current users.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-09-01 11:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 8:09 [PATCH] mfd: syscon: Decouple syscon interface from syscon devices Pankaj Dubey
2014-08-22 8:09 ` Pankaj Dubey
2014-09-01 4:28 ` Pankaj Dubey
2014-09-01 4:28 ` Pankaj Dubey
2014-09-01 7:49 ` Lee Jones
2014-09-01 7:49 ` Lee Jones
2014-09-01 10:37 ` Arnd Bergmann
2014-09-01 10:37 ` Arnd Bergmann
2014-09-01 11:25 ` Lee Jones [this message]
2014-09-01 11:25 ` Lee Jones
2014-09-01 14:24 ` Arnd Bergmann
2014-09-01 14:24 ` Arnd Bergmann
2014-09-01 16:04 ` Lee Jones
2014-09-01 16:04 ` Lee Jones
2014-09-01 17:05 ` Arnd Bergmann
2014-09-01 17:05 ` Arnd Bergmann
2014-09-02 8:05 ` Lee Jones
2014-09-02 8:05 ` Lee Jones
2014-09-02 8:14 ` Arnd Bergmann
2014-09-02 8:14 ` Arnd Bergmann
2014-09-02 8:32 ` Pankaj Dubey
2014-09-02 8:32 ` Pankaj Dubey
2014-09-02 8:34 ` Lee Jones
2014-09-02 8:34 ` Lee Jones
2014-09-01 11:35 ` Pankaj Dubey
2014-09-01 11:35 ` Pankaj Dubey
2014-09-01 14:18 ` Arnd Bergmann
2014-09-01 14:18 ` Arnd Bergmann
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=20140901112549.GM7374@lee--X1 \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=chow.kim@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--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=pankaj.dubey@samsung.com \
--cc=t.figa@samsung.com \
--cc=thomas.ab@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.