From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@denx.de (Pavel Machek) Date: Tue, 1 Oct 2019 11:19:20 +0200 Subject: [cip-dev] Xiling MPSOC -- was Re: CIP IRC weekly meeting today In-Reply-To: <20191001084749.GA1630@amd> References: <20191001084749.GA1630@amd> Message-ID: <20191001091920.GA2353@amd> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org Hi! > > The current work which contains all CIP kernel files is compiled into a tar ball, and I uploaded the ball under the following repository. > > https://github.com/masashi910/tmp-cip-xilinx-mpsoc/ > > Thanks, let me take a look. > > For the record, way to get the files is ... > I diffed that against v4.19.56; which unfortunately produced unclean > diff as it now also includes the -cip changes. I quickly reviewed and > hand-edited the diff. > > I notice this includes staging drivers. > > +obj-$(CONFIG_XILINX_APF) += apf/ > +obj-$(CONFIG_XILINX_FCLK) += fclk/ > > I believe you should get those reviewed and moved outside of staging > before attempting to backport them. > > Otherwise I don't see anything too scary. >>From my point of view, I don't see anything that would prevent merge to -cip. Steps to take would be: a) Identify minimum usable subset of the patches. That would likely be "whatever is neccessary to get some kind of output on serial console", probably clock, pinctrl, serial, dts. b) Verify that support is already in mainline, submit neccessary patches if not. c) Add this point it may be useful to start running tests of mainline on your LAVA board. d) Probably send a list of patches that will be needed for initial boot. e) Start submitting patches for review & merge. Thanks and best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: