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:   Sun, 08 Jan 2023 09:49:17 +0100
From:   Robert Jarzmik <robert.jarzmik@...e.fr>
To:     Arnd Bergmann <arnd@...nel.org>
Cc:     Robert Jarzmik <robert.jarzmik@...e.fr>,
        Daniel Mack <daniel@...que.org>,
        Haojian Zhuang <haojian.zhuang@...il.com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Arnd Bergmann <arnd@...db.de>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        linux-clk@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-mmc@...r.kernel.org
Subject: Re: [PATCH 04/27] ARM: pxa: drop pxa310/pxa320/pxa93x support


Arnd Bergmann <arnd@...nel.org> writes:
> There is currently no devicetree support for any of these three
> SoCs, and no board files remain. As it seems unlikely that 
> anyone
> is going to add DT support soon, let's drop the SoC specific 
> code
> now.

Hi Arnd,

Here you're dropping pxa variant support. For the currently 
"partly" working
boards in devicetree, such a zylonite, this will break their 
current support.

For example the zylonite I have which is working on DT has a 
pxa310 variant.
The cm-x300, which also works in DT, has a pxa320 variant.

What these boards need is their IO mappings and cpufreq to still 
work after
your serie in DT. What bothers me are the changes to :
 - drivers/clk/pxa/clk-pxa3xx.c
 - drivers/cpufreq/pxa3xx-cpufreq.c

Here the clock changes will probably remove the clock provided to 
specific
pxa310/pxa320 drivers for example.

I don't know how you want to proceed, yet this change will break 
some pxa3xx
platforms.

Cheers.

--
Robert

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ