On Fri, Dec 14, 2018 at 03:37:47AM +0000, Aisheng Dong wrote:

quoted

-----Original Message-----
From: Shawn Guo [mailto:shawnguo@kernel.org]
On Fri, Dec 14, 2018 at 02:17:04AM +0000, Aisheng Dong wrote:

quoted

[...]

quoted

quoted

Note: It depends on SCU driver which has already been merged by

Shawn.

quoted

quoted

quoted

So this patch series could go through Shawn's tree as well.

To be clear, I'm not going to take this via my tree, and it
definitely needs to go through clk tree.  If there is a dependency
on my tree, you will likely need to wait for the dependency to land on

mainline and then retry.

quoted

quoted

Sorry, I should have corrected that comment.
It's not depend on SCU driver which is already in the Stephen's tree.
It actually depends on the resource ID definitions[1] and the
centralized PM related service definitions headifle in in power domain
series which is already in your tree.

[2] can be fixed by defining them in clock driver.
But [1] seems can't be fixed as resource ID is shared by power domain
and possible many other SCU client drivers.

Any suggestion?

After [1] and [2] land on v4.21-rc1, you rebase the series on that.  The
dependency will be gone, right?  This is what I suggested above.

Okay, that may need a few more weeks.
BTW, after v4.21-rc1 is out, can the mx8qxp CLK and DTS hit the final v4.21 release?
As I understand, usually we don't receive new feature patch after the first RC,
right?

Yes, they will have to land on 4.22 then.

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel