From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Pankaj Dubey" <pankaj.dubey@samsung.com>
Cc: kgene.kim@samsung.com, linux@arm.linux.org.uk,
naushad@samsung.com, "'Tomasz Figa'" <t.figa@samsung.com>,
linux-kernel@vger.kernel.org, joshi@samsung.com,
linux-samsung-soc@vger.kernel.org, thomas.ab@samsung.com,
tomasz.figa@gmail.com, vikas.sajjan@samsung.com,
chow.kim@samsung.com, lee.jones@linaro.org,
"'Michal Simek'" <michal.simek@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
"'Arnd Bergmann'" <arnd@arndb.de>
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from platform devices
Date: Thu, 04 Sep 2014 08:52:47 +0400 [thread overview]
Message-ID: <1409806367.933281809@f338.i.mail.ru> (raw)
In-Reply-To: <002601cfc7fa$39413580$abc3a080$@samsung.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2441 bytes --]
Thu, 04 Sep 2014 10:09:19 +0530 Ð¾Ñ Pankaj Dubey <pankaj.dubey@samsung.com>:
> Hi Arnd,
>
> On Tuesday, September 02, 2014 Arnd Bergmann wrote,
> > To: Pankaj Dubey
> > Cc: linux-arm-kernel@lists.infradead.org;
> linux-samsung-soc@vger.kernel.org; linux-
> > kernel@vger.kernel.org; lee.jones@linaro.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@gmail.com; Tomasz Figa; Alexander Shiyan; Michal Simek
> > Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
> platform
> > devices
...
> > > -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.
> >
>
> Ok as per our last discussion you mentioned that clps71xx will be soon
> migrating to DT.
> So if that is not going to happen sooner, I would also prefer better keep
> syscon_regmap_lookup_by_pdevname and syscon platform_driver for non-DT case,
> so that this issue should not block this patch.
>
> So please let's make final call to keep syscon platform_driver for non-DT
> case which eventually
> can be dropped once clps71xx driver migrates to DT based. So that I can
> prepare next patchset
> keeping syscon platform_driver support and syscon_regmap_lookup_by_pdevname
> API support
> for non-DT case and send across for review.
Arnd, can you force the applying of the latest clps711x patches to accelerate the process?
I mean latest 3 arm-soc patches from Aug, 19.
After that I will need to make a patch for the SPI and TTY subsystems, then initial DT
support will be introduced.
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-09-04 4:53 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
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 [this message]
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=1409806367.933281809@f338.i.mail.ru \
--to=shc_work@mail.ru \
--cc=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=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).