linux-kernel - Re: [RFC PATCH 1/4] ARM: dts: dra7: Keep usb_otg_ss3 and usb_otg

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: <20190403150901.GR49658@atomide.com>
Date:   Wed, 3 Apr 2019 08:09:01 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Roger Quadros <rogerq@...com>
Cc:     nsekhar@...com, s-anna@...com, linux-kernel@...r.kernel.org,
        Nishanth Menon <nm@...com>, Lokesh Vutla <lokeshvutla@...com>,
        "Kristo, Tero" <t-kristo@...com>
Subject: Re: [RFC PATCH 1/4] ARM: dts: dra7: Keep usb_otg_ss3 and usb_otg_ss4
 disabled

* Roger Quadros <rogerq@...com> [190403 14:54]:
> Below patch is just to get initial feedback. Is the overall approach of splitting
> into DRA7 vs AM5 dtsi files OK?

Yes makes sense to me. And if the devices are on the interconnect but not
fully functional, we probably want to set the status = "disabled" only for
the child to idle the module on init. If the whole device is missing then
not adding it at all for certain SoC variants makes sense.

Regards,

Tony