linux-kernel - Re: [PATCH v4] amba: Remove deferred device addition

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: <20220713145827.yxeoqj6vmkzhrrpv@bogus>
Date:   Wed, 13 Jul 2022 15:58:27 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     Saravana Kannan <saravanak@...gle.com>
Cc:     Marek Szyprowski <m.szyprowski@...sung.com>,
        Russell King <linux@...linux.org.uk>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Rob Herring <robh@...nel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Sudeep Holla <sudeep.holla@....com>,
        John Stultz <john.stultz@...aro.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Kefeng Wang <wangkefeng.wang@...wei.com>,
        kernel-team@...roid.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] amba: Remove deferred device addition

On Tue, Jul 12, 2022 at 12:38:33PM -0700, Saravana Kannan wrote:
> Sudeep,
> 
> This makes me think the issue you are seeing is related to your
> hardware drivers. Can you look into those please? I'm leaning towards
> merging this amba clean up and adding delays (say 1ms) to your
> clock/power domain drivers to avoid the crash you are seeing. And then
> you can figure out the actual delays needed and update it.

I haven't got a chance to debug the issue on Juno much further. One thing
about the platform is that we can't turn off the debug power domain that
most of the coresight devices share.

One thing I also observed with -next+this patch is that with a little log
it can access the registers while adding first few devices and then crash
which doesn't align with platform behaviour as we can't turn off the domain
though we attached and turn on in amba_read_periphid and then turn off and
detach the power domain. Ideally if first device amba_read_periphid was
successful, it must be the case for all, but I see different behaviour.

I need to check again to confirm if it is issue with platform power domain
driver. It is based on SCMI so there is some role played by the f/w as well.

--
Regards,
Sudeep