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]
Date:   Tue, 24 Jan 2017 17:24:33 +0100
From:   Paul Kocialkowski <contact@...lk.fr>
To:     Peter Rosin <peda@...ntia.se>,
        Stephen Warren <swarren@...dotorg.org>
Cc:     linux-kernel@...r.kernel.org, Sebastian Reichel <sre@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>, linux-pm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
        Jon Hunter <jonathanh@...dia.com>
Subject: Re: [PATCH v3] dt-bindings: power: supply: bq24735: reverse the
 polarity of ac-detect

Le jeudi 15 décembre 2016 à 18:50 +0100, Peter Rosin a écrit :
> The bindings are fine.
> 
> The Tegra dts files are buggy, but the driver is also buggy, so those
> two bugs cancel each other. So, the option is to either introduce
> regressions by fixing the two bugs thus creating a flag day where
> the kernel and dt needs to match. Or, just document what is going on
> and change the bindings even if they are not wrong.

After reading the discussion, I would rather be in favor of fixing the driver
and the tegra dts files, which are both wrong.

Keeping things as-is is very counter-intuitive: the GPIO on nyan boards is
active-low and should be described as such (think of other projects, like
U-Boot, reusing the dts). It's also very counter-intuitive to require that any
new board using that driver use active-low polarity in the GPIO declaration when
the line is really active-high.

So yes, it means that older dtbs won't work with new kernels and vice-versa, but
as it was pointed out, this is a bug fix, not even a cosmetic change.

Is anyone strongly opposed to that solution? I'd really rather see the issue
fixed that way instead of the current proposal (this patch).

I'd also be happy to implement and test that solution on nyans, as I've done
other bq24735-related work for nyans recently.

-- 
Paul Kocialkowski, developer of free digital technology at the lower levels

Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ