Message-ID: <dfc2c2c442af55f64e147c920585cb7e6a74939f.camel@codeconstruct.com.au>
Subject: Re: [PATCH v5 1/2] dt-bindings: i2c: Add support for ASPEED i2Cv2
From:   Jeremy Kerr <jk@codeconstruct.com.au>
To:     Ryan Chen <ryan_chen@aspeedtech.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Joel Stanley <joel@jms.id.au>,
        Andrew Jeffery <andrew@aj.id.au>,
        Philipp Zabel <p.zabel@pengutronix.de>,
        "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Date:   Mon, 20 Feb 2023 19:24:08 +0800
In-Reply-To: <TYZPR06MB5274714E58C319B4FE3B6E1BF2A49@TYZPR06MB5274.apcprd06.prod.outlook.com>
References: <20230220061745.1973981-1-ryan_chen@aspeedtech.com>
         <20230220061745.1973981-2-ryan_chen@aspeedtech.com>
         <2141e513acc750bf26775f5b435f4dccd41244aa.camel@codeconstruct.com.au>
         <TYZPR06MB5274714E58C319B4FE3B6E1BF2A49@TYZPR06MB5274.apcprd06.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.3-1 
MIME-Version: 1.0
Precedence: bulk

Hi Ryan,

> > > +=C2=A0 clock-frequency:
> > > +=C2=A0=C2=A0=C2=A0 description:
> > > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Desired I2C bus clock frequency in Hz=
. default 100khz.
> > > +
> > > +=C2=A0 multi-master:
> > > +=C2=A0=C2=A0=C2=A0 type: boolean
> > > +=C2=A0=C2=A0=C2=A0 description:
> > > +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that there is another master a=
ctive on this bus
> >=20
> > These are common to all i2c controllers, but I see that i2c-controller.=
yaml
> > doesn't include them (while i2c.text does).
> >=20
> > I assume we're OK to include these in the device bindings in the meanti=
me.
> > But in that case, you may also want to include the common "smbus-alert"
> > property, which you consume in your driver.
> >=20
> Since i2c.text have multi-master, smbus-alert. I don't need those two rig=
ht?

Depends whether the maintainers consider i2c.text as part of the
schema, I figure. Might be best to get their input on this.


> > > +=C2=A0 timeout:
> > > +=C2=A0=C2=A0=C2=A0 type: boolean
> > > +=C2=A0=C2=A0=C2=A0 description: Enable i2c bus timeout for master/sl=
ave (35ms)
> > > +
> > > +=C2=A0 byte-mode:
> > > +=C2=A0=C2=A0=C2=A0 type: boolean
> > > +=C2=A0=C2=A0=C2=A0 description: Force i2c driver use byte mode trans=
mit
> > > +
> > > +=C2=A0 buff-mode:
> > > +=C2=A0=C2=A0=C2=A0 type: boolean
> > > +=C2=A0=C2=A0=C2=A0 description: Force i2c driver use buffer mode tra=
nsmit
> >=20
> > These three aren't really a property of the hardware, more of the inten=
ded
> > driver configuration. Do they really belong in the DT?
> >=20
> Sorry, I am confused.=20
> This is hardware controller mode setting for each i2c transfer.=20
> So I add it in property for change different i2c transfer mode.
> Is my mis-understand the property setting?

It depends what this is configuration is for.

Would you set the transfer mode based on the design of the board? Is
there something about the physical i2c bus wiring (or some other
hardware design choice) that would mean you use one setting over
another?

On the other hand, if it's just because of OS behaviour, then this
doesn't belong in the DT.

Maybe to help us understand: why would you ever *not* want DMA mode?
Isn't that always preferable?

Cheers,


Jeremy