linux-kernel - Re: [BUG] SPI broken for SPI based panel drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201202121956.GA5560@sirena.org.uk>
Date:   Wed, 2 Dec 2020 12:19:56 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Sven Van Asbroeck <thesven73@...il.com>
Cc:     "H. Nikolaus Schaller" <hns@...delico.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        kernel list <linux-kernel@...r.kernel.org>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>,
        Andreas Kemnade <andreas@...nade.info>
Subject: Re: [BUG] SPI broken for SPI based panel drivers

On Tue, Dec 01, 2020 at 01:43:36PM -0500, Sven Van Asbroeck wrote:
> On Tue, Dec 1, 2020 at 12:13 PM H. Nikolaus Schaller <hns@...delico.com> wrote:

> > I am not sure if DT maintainers accept that we revert a DT change just to
> > handle some change in a driver. Usually they insist on fixing a driver and
> > live with the DT. DT is carved in stone or could be ROM...

> This is above my paygrade, but I've always assumed that the devicetree ABI
> is an in-kernel ABI, i.e. not a userspace ABI. Meaning that it is flexible and
> there is no obligation to keep it 100% backwards compatible. Of course Rob
> Herring may want to keep it as backwards-compatible as possible, but that's
> an altogether different thing from having a userspace-type ABI.

It's supposed to be an ABI, though sometimes that gets broken - in a
case like this if there's only a very limited set of users relying on
something that's going to make things harder to maintain and which don't
in practice distribute the kernel separately to the DT then it can make
sense to just break the DT since realistically nobody's going to
actually notice.  On the other hand if people are distributing the
kernel separately to the DT then compatibility definitely has to be
maintained.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)