linux-kernel - Re: [PATCH] ARM: dts: mvebu: Add device tree for RD-AC3X-48G4X2XL board

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]

Message-ID: <20201124221501.GI2036992@lunn.ch>
Date:   Tue, 24 Nov 2020 23:15:01 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc:     Aryan Srivastava <Aryan.Srivastava@...iedtelesis.co.nz>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "gregory.clement@...tlin.com" <gregory.clement@...tlin.com>,
        "sebastian.hesselbarth@...il.com" <sebastian.hesselbarth@...il.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: dts: mvebu: Add device tree for RD-AC3X-48G4X2XL
 board

> > +&i2c0 {
> > +	pinctrl-names = "default";
> > +	pinctrl-0 = <&i2c0_pins>;
> > +	status = "okay";
> > +
> > +	eeprom@53{
> > +		compatible = "atmel,24c64";
> > +		reg = <0x53>;
> > +	};
> > +//	cpld@3c{
> > +//		compatible = "marvell,ac3x-cpld";
> > +//		reg = <0x3c>;
> > +//	};
> > +};
> 
> Question for the mvebu maintainers: We know there is a cpld with that 
> can be interfaced with over i2c. Other than detecting that it shows up 
> on the i2c bus we haven't done anything with it. We believe it 
> interfaces with some discrete IO and might mux the i2c interface towards 
> the SFP/QSFP cages.
> 
> Obviously there isn't a "marvell,ac3x-cpld" driver (yet) so I suggested 
> to Aryan that we put it in the dts to document its existence but leave 
> it commented out for now. Is this OK?

Hi Chris

I would just add a text comment, not DT. We have no idea what this
node will look like until we have the driver.

Is there an open source 'vendor crap driver'? Do we have anything to
go on?

     Andrew