linux-kernel - Re: [PATCH v1 11/13] dt-bindings: power: add PX30 SoCs header for power-domain

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]

Date:   Sun, 13 May 2018 22:53:00 +0200
From:   Heiko Stübner <heiko@...ech.de>
To:     Tao Huang <huangtao@...k-chips.com>
Cc:     Elaine Zhang <zhangqing@...k-chips.com>, mark.rutland@....com,
        devicetree@...r.kernel.org, ulf.hansson@...aro.org,
        khilman@...nel.org, xxx@...k-chips.com, linux-pm@...r.kernel.org,
        rjw@...ysocki.net, linux-kernel@...r.kernel.org, xf@...k-chips.com,
        linux-rockchip@...ts.infradead.org, robh+dt@...nel.org,
        Finley Xiao <finley.xiao@...k-chips.com>,
        linux-arm-kernel@...ts.infradead.org, wxt@...k-chips.com
Subject: Re: [PATCH v1 11/13] dt-bindings: power: add PX30 SoCs header for power-domain

Hi,

Am Sonntag, 13. Mai 2018, 17:18:12 CEST schrieb Tao Huang:
> Hi Heiko:
> 
> On 2018年05月12日 06:11, Heiko Stuebner wrote:
> > Here I have a naming question. When looking at the vendor kernel
> > it looks like the px30 is largely related to the rk3326.
> > (rk3326.dtsi includeing the px30.dtsi)
> > 
> > What is the reason for basing the naming on the px30 this time? And could
> > we possibly keep to rkXXXX names for the basic things in the kernel, thus
> > keeping the pxXX as second name, like with the other px-variants before?
> 
> PX30 and RK3326 are different chips. PX30 has more features. You can simply
> think that RK3326 is a subset of PX30. The RK3326 is more like a PX30
> derivative chip. This is not the same as the previous chips. So we use PX30
> instead of RK3326 for name, and the opening document is only for PX30, we
> think this is more convenient for developers.

ok, sounds reasonable :-) ... So we'll stay with the PX30.


Heiko