linux-kernel - Re: [PATCH v8 10/13] dt-bindings: mips: cpu: Add property for broken HCI information

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: <ZyOXcrS/7txCQU3B@alpha.franken.de>
Date: Thu, 31 Oct 2024 15:42:58 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Gregory CLEMENT <gregory.clement@...tlin.com>
Cc: Jiaxun Yang <jiaxun.yang@...goat.com>,
	Aleksandar Rikalo <arikalo@...il.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Vladimir Kondratiev <vladimir.kondratiev@...ileye.com>,
	Theo Lebrun <theo.lebrun@...tlin.com>,
	Arnd Bergmann <arnd@...db.de>, devicetree@...r.kernel.org,
	Djordje Todorovic <djordje.todorovic@...cgroup.com>,
	Chao-ying Fu <cfu@...ecomp.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Greg Ungerer <gerg@...nel.org>, Hauke Mehrtens <hauke@...ke-m.de>,
	Ilya Lipnitskiy <ilya.lipnitskiy@...il.com>,
	linux-kernel@...r.kernel.org,
	"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
	Marc Zyngier <maz@...nel.org>,
	"paulburton@...nel.org" <paulburton@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Serge Semin <fancer.lancer@...il.com>,
	Tiezhu Yang <yangtiezhu@...ngson.cn>
Subject: Re: [PATCH v8 10/13] dt-bindings: mips: cpu: Add property for broken
 HCI information

On Thu, Oct 31, 2024 at 09:13:57AM +0100, Gregory CLEMENT wrote:
> Hi Jiaxun,
> 
> > 在2024年10月29日十月 下午4:11，Jiaxun Yang写道：
> >> 在2024年10月29日十月 下午12:21，Aleksandar Rikalo写道：
> >> [...]
> >>>
> >>>> Is this property applicable for all MIPS vendors? There is no vendor
> >>>> prefix here, so this is generic for this architecture, right?
> >>
> >> I'd say the best vendor prefix is mti in this case.
> >>
> >> CM3 IP block is supplied by MIPS Technology, it is not a part of MIPS
> >> architecture spec.
> >
> > I just tried to revise this problem and I think a better approach would
> > be picking my CM binding [1] patch and add this as a property to CM binding.
> >
> > You don't need to pick rest of that series, this binding alone is sufficient,
> > and it's already being reviewed.
> >
> > Thanks
> > [1]:
> > https://lore.kernel.org/all/20240612-cm_probe-v2-5-a5b55440563c@flygoat.com/
> 
> I had a look at your series and it seems that all the issues raised were
> solved, so why wasn't it merged?

https://lore.kernel.org/all/2xkut5pyzk4b4ugl4ku72y4rfqrfsoxj4aww2jwlgkc3lmd464@zwf773fr7fpq/

so it's still unclear to me, whether there is something to fix or not.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]