Re: [PATCH 1/2] arm64: marvell: dts: fill MachiatoBin board description
From: Thomas Petazzoni
Date: Tue May 16 2017 - 05:55:55 EST
On Tue, 16 May 2017 10:50:27 +0100, Russell King - ARM Linux wrote:
> I can't see how you can say that when the branch contains support for
> SDHCI and ethernet. It obviously will collide, since it conflicts with
> the changes I have.
Correct, but Marcin has submitted patches, and you haven't.
> > The board is starting to get really popular and a lot has been happening
> > around it recently - missing bits like 'chosen' node or the interfaces
> > is pretty annoying.
> Given that features like SDHCI and basic ethernet support have only just
> been merged during the merge window, how about giving those who are
> supporting the platform some time to organise their trees and get patches
> out there, rather than cutting across those who have put considerable
> effort into the platform already, or working with those who have.
I believe if you say that, it's because you don't know how much work
Marcin is doing behind the scenes on supporting Marvell platforms, and
not only at the Linux kernel level.
And it's difficult to buy your argument here, because Marcin is
*precisely* supporting the platform by sending useful patches.
> The whole Armada 8k support is all very new, and there's still lots of
> fundamental bits that are missing - pinmux and gpio are the two biggest
> I've already put effort into cleaning up the mvebu pinmux code (already
> merged) so that we can cleanly merge the pinmux support, but both of
> these are a sticking point with free-electrons - they have a view on
> how it should be represented in DT which does not fit with the current
> orion-gpio usage, nor with the "system controller" being in drivers/clk.
GrÃgory Clement has been working on this, and he has a patch series
almost ready to submission.
> The code which I have in my tree is correct for the Armada 8k hardware
> (which has some weirdness about which gpios on each CP110 appear to the
> external world - some are used for inter-CP110 communication and must
> not be exposed) so any additional work should be based on the code in
> my tree.
No, there is no rule like this in the kernel community. Whatever is in
your private tree does not matter. Until it gets submitted, it doesn't
exist, and nobody is forced to base its work on top of your
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering