[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180801061515.krn52iaq2kqdi3wo@localhost>
Date: Tue, 31 Jul 2018 23:15:15 -0700
From: Richard Cochran <richardcochran@...il.com>
To: "Y.b. Lu" <yangbo.lu@....com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Madalin-cristian Bucur <madalin.bucur@....com>,
Rob Herring <robh+dt@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
"David S . Miller" <davem@...emloft.net>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] ptp_qoriq: convert to use module parameters for
initialization
On Wed, Aug 01, 2018 at 04:36:40AM +0000, Y.b. Lu wrote:
> Could I add a function to calculate a set of default register values
> to initialize ptp timer when dts method failed to get required
> properties in driver?
Yes, it would be ideal if the driver can pick correct values
automatically.
However, the frequency on the FIPER outputs can't be configured
automatically, and we don't have an API for the user to choose this.
> I think this will be useful. The ptp timer on new platforms (you may
> see two dts patches in this patchset. Many platforms will be
> affected.) will work without these dts properties. If user want
> specific setting, they can set dts properties.
Sure.
Thanks,
Richard
Powered by blists - more mailing lists