From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org,
Alexander Shiyan <shc_work@mail.ru>
Cc: kgene.kim@samsung.com, linux@arm.linux.org.uk,
naushad@samsung.com, lee.jones@linaro.org,
Tomasz Figa <t.figa@samsung.com>,
linux-kernel@vger.kernel.org, joshi@samsung.com,
linux-samsung-soc@vger.kernel.org, thomas.ab@samsung.com,
Pankaj Dubey <pankaj.dubey@samsung.com>,
vikas.sajjan@samsung.com, chow.kim@samsung.com,
tomasz.figa@gmail.com, Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from platform devices
Date: Tue, 02 Sep 2014 19:40:45 +0200 [thread overview]
Message-ID: <3685403.qLrNHfR1Kx@wuerfel> (raw)
In-Reply-To: <1409672572.303525842@f75.i.mail.ru>
On Tuesday 02 September 2014 19:42:52 Alexander Shiyan wrote:
> > > -struct regmap *syscon_regmap_lookup_by_pdevname(const char *s)
> > > -{
> > > - struct device *dev;
> > > - struct syscon *syscon;
> > > -
> > > - dev = driver_find_device(&syscon_driver.driver, NULL, (void *)s,
> > > - syscon_match_pdevname);
> > > - if (!dev)
> > > - return ERR_PTR(-EPROBE_DEFER);
> > > -
> > > - syscon = dev_get_drvdata(dev);
> > > -
> > > - return syscon->regmap;
> > > -}
> > > -EXPORT_SYMBOL_GPL(syscon_regmap_lookup_by_pdevname);
> >
> > I think this can actually be left intact if that helps with clps71xx.
> > It could be done in a hacky way using bus_find_device_by_name()
> > to keep it simple, or in a somewhat nicer way by keeping the
> > syscon platform_driver around for the non-DT case.
>
> It will not work anyway because the patch involves the use of
> of_device_is_compatible(), of_iomap() etc...
What I meant was to have the pdevname stuff keep working the way
it does today. At that point, you essentially have two completely
independent drivers, one that registers a platform driver and
provides syscon_regmap_lookup_by_pdevname, and one that provides
the other interfaces using DT lookup.
Arnd
next prev parent reply other threads:[~2014-09-02 17:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 14:42 [PATCH v2] mfd: syscon: Decouple syscon interface from platform devices Pankaj Dubey
2014-09-02 14:50 ` Tomasz Figa
2014-09-02 15:20 ` Arnd Bergmann
2014-09-02 15:42 ` Alexander Shiyan
2014-09-02 17:40 ` Arnd Bergmann [this message]
2014-09-03 13:16 ` Boris BREZILLON
2014-09-03 13:49 ` Arnd Bergmann
2014-09-03 14:15 ` Boris BREZILLON
2014-09-04 4:45 ` Pankaj Dubey
2014-09-04 6:03 ` Boris BREZILLON
2014-09-05 8:14 ` Boris BREZILLON
2014-09-16 11:53 ` Pankaj Dubey
2014-09-16 14:52 ` Arnd Bergmann
2014-09-04 4:39 ` Pankaj Dubey
2014-09-04 4:52 ` Alexander Shiyan
2014-09-03 3:44 ` Vivek Gautam
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=3685403.qLrNHfR1Kx@wuerfel \
--to=arnd@arndb.de \
--cc=chow.kim@samsung.com \
--cc=joshi@samsung.com \
--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=michal.simek@xilinx.com \
--cc=naushad@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=shc_work@mail.ru \
--cc=t.figa@samsung.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).