On Thu, Oct 05, 2023 at 04:51:50PM +0200, Gregory CLEMENT wrote: > Hello Serge(y), > > > On Wed, Oct 04, 2023 at 06:10:32PM +0200, Gregory CLEMENT wrote: > >> The MIPS Warrior I-class I6500 was announced by Imagination > >> Technologies in 2016 and is used in the Mobileye SoC EyeQ5. > >> > >> Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxx> > >> --- > >> Documentation/devicetree/bindings/mips/cpus.yaml | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/Documentation/devicetree/bindings/mips/cpus.yaml b/Documentation/devicetree/bindings/mips/cpus.yaml > >> index cf382dea3922..87fd2842ba68 100644 > >> --- a/Documentation/devicetree/bindings/mips/cpus.yaml > >> +++ b/Documentation/devicetree/bindings/mips/cpus.yaml > >> @@ -39,6 +39,7 @@ properties: > >> - mti,mips24KEc > >> - mti,mips14KEc > >> - mti,mips14Kc > > > >> + - mti,i6500 > > > > Since the CPU core vendor is Imagination Technologies thus it would > > be more appropriate to have the "img," prefix. Wouldn't it? > > According to Documentation/devicetree/bindings/vendor-prefixes.yaml > > "^mti,.*": > description: Imagination Technologies Ltd. (formerly MIPS > Technologies Inc.) Yes, "mti" is also marked as Imagination Technologies Ltd, but I doubt we should use "mti" prefix for something what has been developed after Image Tech acquired MIPS Tech. What is the point in having the "img," prefix then? Rob, your opinion? -Serge(y) > > So I think it's OK. > > Gregory > > > > > -Serge(y) > > > >> > >> reg: > >> maxItems: 1 > >> -- > >> 2.40.1 > >> > > -- > Gregory Clement, Bootlin > Embedded Linux and Kernel engineering > http://bootlin.com
