Re: [L4s-discuss] [EXTERNAL] rpi 5 and hardware ptp

rjmcmahon <> Mon, 08 April 2024 18:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E352C151065 for <>; Mon, 8 Apr 2024 11:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.097
X-Spam-Status: No, score=-6.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TcYcI6mboXuc for <>; Mon, 8 Apr 2024 11:08:49 -0700 (PDT)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 3156DC14F61D for <>; Mon, 8 Apr 2024 11:08:49 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTPA id C32301B289; Mon, 8 Apr 2024 11:08:48 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 C32301B289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=bobcat; t=1712599728; bh=oFPTNH1iuOY6da3nXv9PRafgc3MKldjmbCZP7hDmgt8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=EkJsG5RWwj17RRAQhfb3NM19I9MW0zUaOJ7N1Op/1qVP6kOH+povvxt+aMkLqBmMs 3/90fT70mZ+MCUVbg1q4PxTrWmPr19GSyw3vXZnz7PMTU1fUDWPJYuZ/JvkDdCUJyO HmPuRdaR6C/SpJRmA5ze5Yf0vEW7KTILfk+1r04w=
MIME-Version: 1.0
Date: Mon, 08 Apr 2024 11:08:48 -0700
From: rjmcmahon <>
To: "Overcash, Michael (CCI-Atlanta)" <>
Cc: rjmcmahon <>,
In-Reply-To: <>
References: <> <>
Message-ID: <>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [L4s-discuss] [EXTERNAL] rpi 5 and hardware ptp
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Low Latency, Low Loss, Scalable Throughput \(L4S\) " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Apr 2024 18:08:53 -0000

> What about iPhone / Android ecosystems ... is anything possible there?
> Those devices all have integrated GPS already, although I don't know
> if an app could practically utilize it.
I don't know of a way to get either PPS or PTP hardware timestamps on 
those platforms. They do have their own GPS chips and tend to have 
temperature compensated oscillators (TCXO) but not sure how well the 
system clock is synced to the GPS atomic clock. We tend to use reference 
hardware in our rigs for these and not actual devices. The iOS devices 
are even more challenging for many non technical reasons.

It would be great if there was a way to address these platforms to have 
the system clocks always synced to the GPS atomic.