From: Mark Rutland <mark.rutland@arm.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Sathya Prakash M R <sathyap@ti.com>,
"tony@atomide.com" <tony@atomide.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"paul@pwsan.com" <paul@pwsan.com>
Subject: Re: [PATCH v2 4/4] ARM: DTS: AM43x: Add DSS node
Date: Fri, 14 Mar 2014 10:14:06 +0000 [thread overview]
Message-ID: <20140314101405.GI25870@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <5322CF02.4060705@ti.com>
On Fri, Mar 14, 2014 at 09:42:26AM +0000, Tomi Valkeinen wrote:
> On 14/03/14 11:10, Mark Rutland wrote:
>
> > The "simple-bus" compatible string is intended for busses which are
> > transparent (bar some address remapping expressed via ranges), and is
> > not intended as an annotation to get Linux to probe child nodes.
> >
> > Any node with a "simple-bus" entry in the compatible list should either
> > be handled as a transparent bus, or optionally as the more specific bus
> > it claims to be (where some hardware configuration may be required
> > before children can be probed). Unfortunately Linux probes chidlren
> > regardless, which is arguable a Linux bug.
> >
> > There's no reason to leak this issue into dts files. Please remove the
> > "simple-bus" string, and get the dss driver to probe children as
> > required -- as described above the dss node never makes sense as a
> > simple-bus.
>
> Ok. I'll remove the simple-bus, and make the dss_core register the
> devices. I presume of_platform_populate() is fine for this? Seems to
> work fine for registration, but I haven't figured out yet how to
> unregister the devices (I get a crash in platform_device_del() if I just
> call platform_device_unregister for the submodules).
I think of_platform_populate should be ok. It's not fantastic -- all
child nodes will be probed, regardless of whether you expect them to
exist, but it's not as broken as using "simple-bus".
I'm unfortunately not familiar with how unregistration works.
I can't see anything obviously wrong in platform_device_del. Do you have
a backtrace?
Thanks,
Mark.
next prev parent reply other threads:[~2014-03-14 10:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 8:58 [PATCH v2 0/4] Add Display support for AM43xx Sathya Prakash M R
2014-03-13 8:58 ` [PATCH v2 1/4] OMAPDSS: Add DSS features " Sathya Prakash M R
2014-03-13 8:58 ` [PATCH v2 2/4] ARM: AM43xx: fix dpll init in bypass mode Sathya Prakash M R
2014-03-13 10:24 ` Tomi Valkeinen
2014-03-13 10:32 ` Sathya Prakash
2014-03-13 8:58 ` [PATCH v2 3/4] ARM: OMAP2+: AM43xx DSS Hwmod Sathya Prakash M R
2014-03-13 8:58 ` [PATCH v2 4/4] ARM: DTS: AM43x: Add DSS node Sathya Prakash M R
2014-03-13 10:21 ` Tomi Valkeinen
2014-03-13 10:30 ` Sathya Prakash
2014-03-13 17:46 ` Mark Rutland
2014-03-13 18:22 ` Tomi Valkeinen
2014-03-14 9:10 ` Mark Rutland
2014-03-14 9:42 ` Tomi Valkeinen
2014-03-14 10:14 ` Mark Rutland [this message]
2014-03-14 10:19 ` Tomi Valkeinen
2014-03-14 11:07 ` Tomi Valkeinen
2014-03-14 14:07 ` Mark Rutland
2014-03-14 16:04 ` Felipe Balbi
2014-03-14 16:34 ` Tomi Valkeinen
2014-03-14 18:00 ` Mark Rutland
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=20140314101405.GI25870@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rob.herring@calxeda.com \
--cc=sathyap@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).