Re: [PATCH 0/3 - V2] Introducing Device Tree Overlays

From
Pantelis Antoniou <hidden>
Date
2013-11-12 08:17:06
Also in
lkml
Reply to
Grant Likely, 2013-11-12
Hi Grant,

On Nov 11, 2013, at 6:04 PM, Grant Likely wrote:
On Thu, 7 Nov 2013 21:46:26 +0100, Sebastian Andrzej Siewior [off-list ref] wrote:
quoted
On 07.11.13, Pantelis Antoniou wrote:
quoted
Hi Sebastian,
Hi Pantelis,
quoted
FWIW DT has been ported to x86. And is present on arm/powerpc/mips/arc and possibly
others.
Yes, I know. I am the one that did the work for CE4100, the first one
that boots with DT on x86.
quoted
So what are we talking about again? If you care about the non-DT case, why
don't you make a patch about how you could support Guenter's use case on
the x86.
I am only saying that this "hot-plug a device at a non hot-plugagle bus at
runtime" is not limited to DT but this solution is. X86 + ACPI is not
the only limitation. ARM is (forced) going to ACPI as well as far I
know. And this solution is limited to DT. This is what I am pointing
out.
I'm going to nip this in the bud before it spreads...  No.

ARM is not going wholesale to ACPI.  ACPI will be implemented on ARMv8
servers. Don't expect the rest of the ARM world to go there anytime
soon, if at all.

As for being limited to DT, that is correct currently, just as SSDT is
an ACPI specific way of doing mostly the same thing. However, I'm not sure
it needs to be a limitation. As long as there is well definied
segregation between the base tree and the overlay (ie. it would be
useful to filter which nodes can be attached to, there are security
implications here too) then it would be fine for a DT overlay to pull in
additional devices on top of an ACPI base tree.
Well, this can be pretty radical, but what about converting the ACPI base tree
in DT format and then take it from there.

I'm sure the state of DT encompasses most of what ACPI does ATM, modulo the
whole craziness of calling in firmware/interpreting bytecode to do stuff like
turn on a GPIO.

I might be in the minority, but it took us so many years on not having to rely
on weird firmware to get our systems to work, and ACPI seems to be heading back
into the old ways on having to rely on firmware quirks to patch firmware we 
are dependent on.

DT way of describing only, may be not to the liking of everyone, but I certainly
prefer it.
quoted
quoted
His use case is not uncommon, believe it or not, and x86 would benefit from
something this flexible.
I *think* a more flexible solution would be something like bus_type which is
exposed via configfs. It would be attached behind a certain device/bus where
the "physical" hotplug interface is. The user would then be able to read the
configuration based on whatever information he has and could then create
devices he likes at runtime. This wouldn't depend much on the firmware that is
used but would require a little more work I think.
I'm certainly fine with investigating the above (modulo security
concerns of creating arbitrary devices). However, that is only one
use-case. There still needs to be the mechanism of passing the kernel a
blob all at once and say, "Here is the layout of this new hunk of
hardware".  For instance, you don't want to have to build up a set of
devices from scratch every time a new device is passed in. Xilinx for
instance has a tool which creates a FDT for an FPGA bitstream right from
the FPGA tools.

g.
Regards

-- Pantelis

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Thread (44 messages) 44 messages, 12 authors, last reply 2013-11-12
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help