[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <PAWPR10MB823946C2D201CAB2CCFCBDE6F1A1A@PAWPR10MB8239.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 30 Oct 2023 09:28:41 +0000
From: "Stoll, Eberhard" <eberhard.stoll@...tron.de>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>
CC: Miquel Raynal <miquel.raynal@...tlin.com>,
Eberhard Stoll <estl@....net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"Schrempf, Frieder" <frieder.schrempf@...tron.de>,
Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Krishna Yarlagadda <kyarlagadda@...dia.com>,
Leonard Göhrs <l.goehrs@...gutronix.de>,
Yang Yingliang <yangyingliang@...wei.com>
Subject: AW: AW: [PATCH 1/4] spi: Add parameter for clock to rx delay
> So, then the question is what does DT _actually_ describes?
> If we have an autoprobe of something that doesn't work on platform A and
> works
> on platform B, shouldn't these platforms have to have distinguishable DTs?
Yes it's one possibility to deal with it.
But I think the first choice should be to improve the autoprobe function to work
properly on all platforms. This offers the most advantage for all. If this doesn't
work, the DT approach should be the fallback choice.
Improving the autoprobe function in this way seems realistic. So it's currently the
way we should go.
Kind regards
Eberhard
Powered by blists - more mailing lists