[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM7PR04MB6885A1B5973486928FAF7538F8AC0@AM7PR04MB6885.eurprd04.prod.outlook.com>
Date: Tue, 28 Apr 2020 07:37:12 +0000
From: "Y.b. Lu" <yangbo.lu@....com>
To: Richard Cochran <richardcochran@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
Leo Li <leoyang.li@....com>
Subject: RE: [PATCH] ptp_qoriq: output PPS signal on FIPER2 in default
> -----Original Message-----
> From: Richard Cochran <richardcochran@...il.com>
> Sent: Monday, April 27, 2020 9:52 PM
> To: Y.b. Lu <yangbo.lu@....com>
> Cc: netdev@...r.kernel.org; David S . Miller <davem@...emloft.net>; Leo Li
> <leoyang.li@....com>
> Subject: Re: [PATCH] ptp_qoriq: output PPS signal on FIPER2 in default
>
> On Mon, Apr 27, 2020 at 11:39:03AM +0800, Yangbo Lu wrote:
> > Output PPS signal on FIPER2 (Fixed Period Interval Pulse) in default
> > which is more desired by user.
>
> FIPER1 is already 1-PPS by default, and the user can load anything
> they want in the device tree, so I don't really see the need for this
> change.
>
> But, I am not really opposed to it, either.
Thanks a lot, Richard.
Yes, I understand. I just think as the default configuration, PPS may be properer than 100 us period pulse which I don't know used for.
>
> Thanks,
> Richard
Powered by blists - more mailing lists