Hi Michele, Am Donnerstag, 20. Oktober 2022, 13:13:10 CEST schrieb Michele Zuccalà: > > no worries, we'll get you through it :-) > > > > thank you > > > > > actually you want to go the following route: > > > > (1) pick up > > - https://lore.kernel.org/all/20220927075511.3147847-25-clabbe@xxxxxxxxxxxx/ > > - https://lore.kernel.org/all/20220927075511.3147847-26-clabbe@xxxxxxxxxxxx/ > > as a base to work on > > > > (2) create a patch to add your compatible. > > I _think_ after that, the compatible block should looks > > something like: > > > > compatible: > > oneOf: > > - const: rockchip,rk3288-crypto > > - const: rockchip,rk3328-crypto > > - const: rockchip,rk3399-crypto > > - items: > > - const: rockchip,rk3228-crypto > > - const: rockchip,rk3288-crypto > > > > to handle the new dual element compatible. > > make dt_binding_check > > should tell you about a wrong format. > > > > (3) modify your dts patch to use the two compatibles > > (4) export patches by > > git format-patch -2 --cover-letter > > and mention in the cover-letter the dependency on the > > yaml conversion. > > very clear. But excuse the stupid question, this way it becomes a new patchset > and not the v2 of this patch, right?! Will this patch be automatically > ignored ?! The new patchset still should become v2, as it still addresses your overall goal of adding crypto support for the rk3228. Heiko
