From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta0.migadu.com (out-173.mta0.migadu.com [91.218.175.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 66759134AB for ; Sun, 23 Mar 2025 22:22:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742768562; cv=none; b=t6LXiB+aFVrVjoJwXd0693Izk0ZDIW1tR+9YWIljqDYf4FUyXJn4f2K7t4+4n6WTk7e6Bpl+vh4UEdwp7w6p1zKT7pCFPxjii/X9NaEVgHPvPXXBwT69p1fHuls12jbtAtHxM71pNxZp8zsJZaujgW2vWHUuLpE3QuhHv87v38o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1742768562; c=relaxed/simple; bh=UaDSzJEFU3HxiKYeBIN3vLKun7CzCFd06gaVh2Rjc1w=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=eJ6QJgqnEa4fMIWCWFe4eJlIbdoKS8v4p4QqgMnquStX9K65mXPEuzkTeBTqXQRprvmQSCqMRKG4XczBqrn77u3COuflBxgo3Oe9z4v5AFCkbOUfmr87gG1nuHQA207YZnTsn/djZR/Af8kXpl7cgqIFLXV2zd0CZ1HB+X2aEtw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rosenzweig.io; spf=pass smtp.mailfrom=rosenzweig.io; dkim=pass (2048-bit key) header.d=rosenzweig.io header.i=@rosenzweig.io header.b=JDUR9PGO; arc=none smtp.client-ip=91.218.175.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rosenzweig.io Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rosenzweig.io Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=rosenzweig.io header.i=@rosenzweig.io header.b="JDUR9PGO" Date: Sun, 23 Mar 2025 18:22:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rosenzweig.io; s=key1; t=1742768548; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jBdt6K+1FRRtxV1RM4zhQcREKVKV+utbOhrg0IIMgak=; b=JDUR9PGOmfNe81ydDTGeaPgibvwP+SUVdVLswyyJwxIz2iVH8XXxHPVGYF2LC/pY45mjzF PRpvDOQUvJ92PMV32TRGuW9xbOELBG6MGwDpMNq5uyxAUgAP2TEoh0sSBPRgbve6ImHre1 1eKqPR/gkbftnMQ+vixiX7QzCCfCkypI88USsZ/2351OLZSNat8cu+/I5oqvl0Bo3JStWn +RmDK83Pu2Qywy+7pzss7KwJVDVBWdLCYI4/pmycEN5RzH6/An/O/LdaxhxQtoxDWyJqDo bixjdLUYkrjfUCbZdyfX4h/WASPJHOMW6d1s20h5dyAxhZpnpenFdoweKMBh0Q== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Alyssa Rosenzweig To: Faith Ekstrand Cc: David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Miguel Ojeda , Alex Gaynor , Boqun Feng , Gary Guo , =?iso-8859-1?Q?=22Bj=F6rn_Roy_Baron=22?= , Benno Lossin , Andreas Hindborg , Alice Ryhl , Trevor Gross , Janne Grunau , Sven Peter , Jonathan Corbet , Sergio Lopez Pascual , Ryan Houdek , linux-kernel , dri-devel , rust-for-linux , asahi , linux-arm-kernel , linux-doc , Asahi Lina Subject: Re: [PATCH v3] drm: Add UAPI for the Asahi driver Message-ID: References: <20250314-agx-uapi-v3-1-3abf7e74ea2f@rosenzweig.io> <195b507d4b3.b25d0dad175771.7566427576910952468@collabora.com> <195b582682b.121ba4d5e219032.3109114844776468245@collabora.com> Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <195b582682b.121ba4d5e219032.3109114844776468245@collabora.com> X-Migadu-Flow: FLOW_OUT > > > +    /** > > > +     * @user_timestamp_frequency_hz: Timebase frequency for user timestamps > > > +     */ > > > +    __u64 user_timestamp_frequency_hz; > > > > Why is this different? What are user timestamps and how are they different from GPU timestamps? In v4, I've made get_time return nanos which should clarify things. (Since it hides the SoC clock rate from userspace, leaving only the GPU firmware clock rate and nanoseconds as the two time rates to worry about.)