From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Grant Likely <grant.likely@linaro.org>
Cc: Rob Herring <robherring2@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
George Cherian <george.cherian@ti.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>, Kukjin Kim <kgene.kim@samsung.com>,
Vivek Gautam <gautam.vivek@samsung.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Naveen Krishna Chatradhi <ch.naveen@samsung.com>,
Roger Quadros <rogerq@ti.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] of: provide of_platform_unpopulate()
Date: Wed, 31 Jul 2013 17:21:58 +0200 [thread overview]
Message-ID: <20130731152158.GA10501@linutronix.de> (raw)
In-Reply-To: <20130724141958.9156F3E0A24@localhost>
* Grant Likely | 2013-07-24 15:19:58 [+0100]:
>> Was there more breakage than imx6 and amba devices? Your first version
>> had a fallback case for powerpc. Couldn't we do just allow that for more
>> than just powerpc? I'd much rather see some work-around within the core
>> DT code with a warning to prevent more proliferation than putting this
>> into drivers.
>
>It's tricky stuff. I've not figured out a solution I'm happy with.
>Trying to figure out when to apply a work around is hard because the
>resource reservation makes assumptions about the memory range layout
>that doesn't match the assumptions made by device tree code.
I can't really follow. Do you have a simple at hand?
>One /possible/ option is to not add the resources to the devices at all
>when the device is registered and instead resolve them right at bind
>time. Jean Christophe proposed doing this already to solve a different
>problem; obtaining resources that require other drivers to be probed
>first. If the resources are resolved at .probe() time, then the resource
>registration problem should also go away.
>
>The downside to that approach is that it makes each deferred probe more
>expensive; potentially a *lot* more expensive depending on how much work
>the xlate functions have to do. It would be worth prototyping though to
>see how well it works.
So you say defer the io ressources until the device-tree device is
actually probed. I don't really understand why that defer part should
solve the problem but I would try and see how it goes.
Jean-Christophe proposed that only, that means no patches yet, right?
>g.
Sebastian
next prev parent reply other threads:[~2013-07-31 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 18:14 [PATCH] of: provide of_platform_unpopulate() Sebastian Andrzej Siewior
[not found] ` <1374257691-31981-1-git-send-email-bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2013-07-21 14:42 ` Rob Herring
[not found] ` <51EBF33A.4050207-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-07-21 19:47 ` Sebastian Andrzej Siewior
2013-07-21 20:48 ` Rob Herring
[not found] ` <51EC4908.4040504-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-07-21 23:44 ` Grant Likely
2013-07-22 21:16 ` Rob Herring
2013-07-24 14:19 ` Grant Likely
2013-07-31 15:21 ` Sebastian Andrzej Siewior [this message]
2013-07-29 9:33 ` Benjamin Herrenschmidt
2013-07-31 16:28 ` Rob Herring
2013-07-29 9:31 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2013-07-20 5:03 NAVEEN KRISHNA CHATRADHI
2013-07-20 5:43 NAVEEN KRISHNA CHATRADHI
2013-07-22 8:25 ` Sebastian Andrzej Siewior
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=20130731152158.GA10501@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=benh@kernel.crashing.org \
--cc=ch.naveen@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gautam.vivek@samsung.com \
--cc=george.cherian@ti.com \
--cc=grant.likely@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=rogerq@ti.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).