On Mon, 2013-05-13 at 08:02 +0100, Michal Simek wrote:
> Just small overview it is a Xilinx soft core cpu where you can even setup
> some parameters for core itself - multiplier, divider, BS, fpu, cache sizes,
> You have to also compose the whole system and every platform/configuration is
> because you can setup addresses, IP on the bus, IRQs, etc.
> Based on this configuration we have created tcl script which is able to
> DTS directly from Xilinx design tool and it is working quite well for several
> and everybody just use it without any problem.
That sounds very neat!
Does this tcl script live in the kernel tree? If so would you think it
would make sense for it to also migrate to device-tree.git? I'm not at
all sure if that makes sense but if you think it does please let me know
which paths need top be carried over.
> As you see in your repo there is only one microblaze DTS which is for one of
> ancient configuration which none used.
> It means from microblaze point of view we can simple remove it from mainline
> because it is useless.
That will then naturally get propagated over to device-tree.git.
> I also care about arm zynq platform where situation is partially different
> zynq is fixed block but you can add others thing to programmable logic.
> It means for zynq case we are almost in the same situation where every zynq
> platform is using different configuration and that's why fpgas are so great.
> It means for zynq case everybody will need different DTS but will be just good
> to describe or show binding.
> Currently we have just one dts for zc702 xilinx reference board.
> Let's move to my point.
> Based on our experience all xilinx boards don't depend on any dts in the
> linux kernel
> and our users just understand the reason why they should use our tcl script
> DTS generation.
> Back to your point about moving DTSes out of the kernel.
I suppose you are now commenting on the Phase II bit where maintenance
of the DTS moves out of linux.git into device-tree.git, rather than
Phase I work, which is creating a split repo which is automatically
synchronised from linux.git but maintenance remains in linux.git, i.e.
what I'm doing here.
> For microblaze - no problem
> just do it. For arm zynq this is more problematic because there is weird
> for ARM. For example PMU which is out of bus and should be probably in cpu
> Also scu devices, scutimers, watchdog which lie on the bus for our case and we
> need to use PPI interrupt cpu mask. Different clock binding, maybe pinmux
> binding, etc.
> It means from my point of view if binding is correct, no problem to move it
> out of the kernel. If a kernel patch change binding, it is worth for me to
> dts in the kernel too to reflect this change and track this change too.
> My proposal is, let's clean all DTSes in the arm kernel that all platform use
> the same binding where all platforms are just correctly described.
AIUI this split/move isn't intended to change the existing policy, which
is already that DTS files are supposed to remain compatible across
kernel versions and that "flag days" are to be avoided. The split is
supposed to make it harder (if not impossible) to accidentally break
On the other hand I suppose there is an argument to be made for clearing
up the cruft *before* making the split.
Ultimately I think this will be up to Grant & co.
> The reaching this point I would suggest that for arm, arm-soc maintainers
> keep eyes on any dts binding change and all these changes require ACK from
> Rob or Grant
> (like device-tree maintainers).
Yes, once we move onto Phase II I don't expect it will end up being me
that is the DTS maintainer -- I expect the maintenance will remain with
those who take care of it in linux.git today.
My involvement in Phase I is really just to help out with the transition
(ulterior motive: the Xen project would also like to use these DTS
files...) not to perform a "land grab" or take over maintenance etc. I
certainly don't think I am the right person to become the long term
maintainer of device-tree.git!