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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 6 Feb 2023 11:46:35 +0100
From:   Rodolfo Giometti <giometti@...eenne.com>
To:     "N, Pandith" <pandith.n@...el.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Sangannavar, Mallikarjunappa" 
        <mallikarjunappa.sangannavar@...el.com>,
        "D, Lakshmi Sowjanya" <lakshmi.sowjanya.d@...el.com>,
        "T R, Thejesh Reddy" <thejesh.reddy.t.r@...el.com>,
        "Hall, Christopher S" <christopher.s.hall@...el.com>
Subject: Re: PPS functionality for Intel Timed I/O

On 06/02/23 11:16, N, Pandith wrote:
> Hi Rodolfo,

Hi

>> -----Original Message-----
>> From: Rodolfo Giometti <giometti@...eenne.com>
>> Sent: Monday, January 30, 2023 7:57 PM
>> To: N, Pandith <pandith.n@...el.com>
>> Cc: linux-kernel@...r.kernel.org; Sangannavar, Mallikarjunappa
>> <mallikarjunappa.sangannavar@...el.com>; D, Lakshmi Sowjanya
>> <lakshmi.sowjanya.d@...el.com>; T R, Thejesh Reddy
>> <thejesh.reddy.t.r@...el.com>; Hall, Christopher S
>> <christopher.s.hall@...el.com>
>> Subject: Re: PPS functionality for Intel Timed I/O

>> Within kernel sources PPS clients and PPS generators are placed into different
>> directories, so I suppose is better to deploy two different pieces of code.
>>
> We are planning to add a new PPS generator driver in drivers/pps/generators
> i) Can this driver use pps_register_source to register Intel Timed I/O device for pulse generation ?

Nope. This function is for pps clients only. PPS generators should generate 
their pulses according to system clock so they don't needed any registrations at 
all under PPS layer.

> ii) To start/stop pulse, we are planning to add additional sysfs attribute from our main driver.
> Something like : /sys/class/ppsX/enable_pin
> This is needed for users to start/stop pulse generation.

If you are still talking about PPS generators they have no entries under 
/sys/class/ppsX/ (just clients have). So you can add an entry under your driver 
to do so.

>> However pay attention to the fact that a PPS generator should be referred to
>> system's main clock and not to peripherals' clock.
>>
> We can sync with the system time for pulse generation.

Mmm... I'm not sure this is correct since PPS generators should generate their 
pulses according to system clock and not according to their internal clocks even 
if they are synced with the system clock.

Ciao,

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@...eenne.com
Linux Device Driver                          giometti@...ux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ