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] [day] [month] [year] [list]
Message-ID: <CACRpkdawz3YgzccnCXV1auyBRHH-zhcxCa1dakBu3EMF0mG5Gg@mail.gmail.com>
Date:   Thu, 10 Mar 2022 09:53:03 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Charles Mirabile <cmirabil@...hat.com>
Cc:     linux-kernel@...r.kernel.org,
        Serge Schneider <serge@...pberrypi.org>,
        Stefan Wahren <stefan.wahren@...e.com>,
        Nicolas Saenz Julienne <nsaenzju@...hat.com>,
        Mattias Brugger <mbrugger@...e.com>,
        linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, fedora-rpi@...glegroups.com,
        Mwesigwa Guma <mguma@...hat.com>,
        Joel Savitz <jsavitz@...hat.com>
Subject: Re: [PATCH v7 6/6] DO NOT MERGE: full sensehat device tree overlay
 for raspberry pi 4

On Thu, Mar 3, 2022 at 6:43 PM Charles Mirabile <cmirabil@...hat.com> wrote:

> This patch should not be merged - dtbs files are not stored in the
> kernel tree. We just provide this file so the code can be tested.

A problem with that approach is that the DTS files are not reviewed
and that causes quality problems, and another problem is that the
kernel lack examples of real-world systems so people have to scout
to find those and that costs developer time.

I know many people are opposed to having this kind of stuff in the
kernel tree, but I am *for* having this kind of stuff in the kernel tree.

Mainly because there is no working community to shepherd it
otherwise, while we (the kernel maintainers) are still dependent on
there being one.

> +       lsm9ds1-magn@1c {
> +               compatible = "st,lsm9ds1-magn";
> +               reg = <0x1c>;
> +               status = "okay";
> +       };
> +
> +       lsm9ds1-accel@6a {
> +               compatible = "st,lsm9ds1-accel";
> +               reg = <0x6a>;
> +               status = "okay";
> +       };

These should typically have mounting matrices. I doubt they
are mounted according to the identity matrix, because electronics
designers usually have other concerns when layouting PCBs.

See
Documentation/devicetree/bindings/iio/mount-matrix.txt

Yours,
Linus Walleij

Yours,
Linus Walleij

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ