[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B35121C-3BF3-4EF2-BBE6-AA76FA1920E3@aspeedtech.com>
Date: Thu, 2 Dec 2021 02:31:58 +0000
From: Billy Tsai <billy_tsai@...eedtech.com>
To: Zev Weiss <zweiss@...inix.com>
CC: Iwona Winiarska <iwona.winiarska@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Dave Hansen <dave.hansen@...el.com>,
Rob Herring <robh@...nel.org>,
Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>,
Jonathan Corbet <corbet@....net>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Guenter Roeck <linux@...ck-us.net>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Jean Delvare <jdelvare@...e.com>,
Arnd Bergmann <arnd@...db.de>,
Rob Herring <robh+dt@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Dan Williams <dan.j.williams@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
Tony Luck <tony.luck@...el.com>,
Andrew Jeffery <andrew@...id.au>,
Randy Dunlap <rdunlap@...radead.org>,
Olof Johansson <olof@...om.net>
Subject: Re: [PATCH v4 02/13] dt-bindings: Add bindings for peci-aspeed
Hi Zev,
On 2021/12/2, 9:55 AM, "Zev Weiss" <zweiss@...inix.com> wrote:
On Wed, Dec 01, 2021 at 02:38:04AM PST, Billy Tsai wrote:
> >Hi,
> >
> >On 2021/11/23, 10:10 PM, "openbmc on behalf of Iwona Winiarska" <openbmc-bounces+billy_tsai=aspeedtech.com@...ts.ozlabs.org on behalf of iwona.winiarska@...el.com> wrote:
> >
> > Add device tree bindings for the peci-aspeed controller driver.
> >
> > > + aspeed,clock-divider:
> > > + description:
> > > + This value determines PECI controller internal clock dividing
> > > + rate. The divider will be calculated as 2 raised to the power of
> > > + the given value.
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + minimum: 0
> > > + maximum: 7
> > > + default: 0
> > > +
> > > + aspeed,msg-timing:
> > > + description:
> > > + Message timing negotiation period. This value will determine the period
> > > + of message timing negotiation to be issued by PECI controller. The unit
> > > + of the programmed value is four times of PECI clock period.
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + minimum: 0
> > > + maximum: 255
> > > + default: 1
> > > +
> > > + aspeed,addr-timing:
> > > + description:
> > > + Address timing negotiation period. This value will determine the period
> > > + of address timing negotiation to be issued by PECI controller. The unit
> > > + of the programmed value is four times of PECI clock period.
> > > + $ref: /schemas/types.yaml#/definitions/uint32
> > > + minimum: 0
> > > + maximum: 255
> > > + default: 1
> >I suggest deleting these three properties and replacing them with the following
> >
> >aspeed,peci-bit-time:
> > description:
> > The bit time driven by PECI controller. The unit of the value is Hz.
> > minimum: 2000
> > maximum: 1000000
> >
> >And the driver should use this property to caculate the appropriate clock-divider,
> >msg-timing and addr-timing, instead of exposing hardware registers to dts.
> >
> Or perhaps just 'bus-frequency' a la i2c-aspeed, gpio-aspeed-sgpio, etc?
It's a good ideal for the consistency.
Thanks
Best Regards,
Billy Tsai
Powered by blists - more mailing lists