Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp848083pxj; Thu, 17 Jun 2021 15:34:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxfCnY6Lqa4Dd4ebblC78pmlp2rowuw2ZiQCrIi7JUhjpkzmq0Hri1WdZTf0z26uZ/Q6Est X-Received: by 2002:aa7:cb19:: with SMTP id s25mr841911edt.194.1623969241492; Thu, 17 Jun 2021 15:34:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623969241; cv=none; d=google.com; s=arc-20160816; b=eKXr3UiVmPPVii9xqKT9ftathB76+Uu01yTSKasmOByXn8qbqD8T4LCY52nSz8WuF6 dmzqzhubBt3GtGwVMxVVKfzwU08QHZXXnHunUPrOpX+tRrk8hPc2eHjDCZH5E8cn3j8m HQsHcURiuMLi2ElrKDY8dm0OtyDcDRGaIoUNYdALy+fspw/H8Asw43jh6lZt/twM/I4P yYuLkqaCQqjR4SKC5iQJDMBldUQ5asq0ueNdJgrdbJsFCHUZH1AqjzKLU2ikTMpuOemF Vb4UasU9k5hKmBlLfuhxp6zin0WHi+dnLcD/jT9FbIH3pa/Qb0IBiSau/Kp+Q+S8nv+O bczw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=7MHD7EiSpY3e0ERtwOHvIB+KaRhM2Um7f/06TGmH7Gg=; b=desVDVTybl26lt6Ng/2uVMEGA4t4ol34SO4xhJNtq80HCY+PpFN9UKPJMq+8ZAD04k LuM2zYzU4qvh/rOFu6qrD0BS4DKlh5hmrZaEpQ94AVJ+Hmyf4UIjlw/9V4qLoLknBDF2 MW8fyH77PhT18GWjGhyF9oEkaBElrf2AId2S+/3oxim71WkcQR98lhb+WZkscssCsqFn E7XatyfE8qOktNufYjlEN2Y7RQpFFTBPS8L0EfSLK4jWFqA853nAr/adV/TCdyWAZ7H/ qzEzDxBa/D+4sr4TqA5IxAxBSKFT/fwwMsW/Vr1sYjs6mwaX2ur6oc/oWVqHhPN2j8c6 DzSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ISiz3+CB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i16si2787165edv.251.2021.06.17.15.33.39; Thu, 17 Jun 2021 15:34:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ISiz3+CB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231872AbhFQRpD (ORCPT + 99 others); Thu, 17 Jun 2021 13:45:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230288AbhFQRpC (ORCPT ); Thu, 17 Jun 2021 13:45:02 -0400 Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2496BC061574; Thu, 17 Jun 2021 10:42:54 -0700 (PDT) Received: by mail-ej1-x631.google.com with SMTP id l1so11237660ejb.6; Thu, 17 Jun 2021 10:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=7MHD7EiSpY3e0ERtwOHvIB+KaRhM2Um7f/06TGmH7Gg=; b=ISiz3+CBB3cS1Fjzms1hdR9IOCuWXdV/3OZsAmuGA0u24iyp1VIHRdmDtsT0ZCTDEr 6xRvIJTzHq19O7CIonVqvqT5KoNboIJFFofrV9S1qL6xWomF76y1mqpy96Ayf09PDu8Y 1F/iId/lDj1MLIEAdk7KjCspqeheaGab+uxzjCKK+tRfDzZi73Scn+qjPBfxHRJniFVl Mh3LLnvEYE8eiKmUVob2T5c0J84jhYChrB+V3br1n5fVFc1nhVxZlUQPGbiF/zQqroVs iwuUT0RO25hRq1026WPDY/sFUqqW89zfqf7etBnfS8mRpohw9uv5ffFsayrcCTX+EUU4 UFAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7MHD7EiSpY3e0ERtwOHvIB+KaRhM2Um7f/06TGmH7Gg=; b=kHEQP+8i58cnd2kmN3dFcUUxo9uPyn/OMAUWUkJcKdCARAiDlg35krq9jn4Zj5haUL HQsmzTgTDCp1AuWosOvmvpP/0bx28yqL34mjJ8M7OUS4SklwFEzKiN1RGL5C0EdcrOKH aFyoooRdANdisBNGT6ZuVIV1FxD+q1aQj1z+7FpiBh7uCvXr+seLLAGkmVJ0mBqiegw4 JE53Fxo2kuqcgV2I5pykiRW54WZHAjOMRiJsE0oTlyBdfroBTsRnnRlA7gE7BTFtDE1h HMUdiEDuqpwoK44XrppKQPqrgnRJsWUVTriX3clRyvvwuudyqOFRKyc/+3DNFn4UhkmX vSwA== X-Gm-Message-State: AOAM533M2YRA+Di00pQtKOrL1KayuUGzUf767iSyehXlOd/8tCf5KUUv kymQrJ2bdYQvva32WnQ3CdU= X-Received: by 2002:a17:907:3f08:: with SMTP id hq8mr6490774ejc.150.1623951772740; Thu, 17 Jun 2021 10:42:52 -0700 (PDT) Received: from localhost ([185.246.22.209]) by smtp.gmail.com with ESMTPSA id b10sm4776610edf.77.2021.06.17.10.42.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Jun 2021 10:42:52 -0700 (PDT) Date: Thu, 17 Jun 2021 19:42:47 +0200 From: Richard Cochran To: Yangbo Lu Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, mptcp@lists.linux.dev, "David S . Miller" , Jakub Kicinski , Mat Martineau , Matthieu Baerts , Shuah Khan , Michal Kubecek , Florian Fainelli , Andrew Lunn , Rui Sousa , Sebastien Laveze Subject: Re: [net-next, v3, 02/10] ptp: support ptp physical/virtual clocks conversion Message-ID: <20210617174247.GB4770@localhost> References: <20210615094517.48752-1-yangbo.lu@nxp.com> <20210615094517.48752-3-yangbo.lu@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210615094517.48752-3-yangbo.lu@nxp.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 15, 2021 at 05:45:09PM +0800, Yangbo Lu wrote: > diff --git a/Documentation/ABI/testing/sysfs-ptp b/Documentation/ABI/testing/sysfs-ptp > index 2363ad810ddb..2ef11b775f47 100644 > --- a/Documentation/ABI/testing/sysfs-ptp > +++ b/Documentation/ABI/testing/sysfs-ptp > @@ -61,6 +61,19 @@ Description: > This file contains the number of programmable pins > offered by the PTP hardware clock. > > +What: /sys/class/ptp/ptpN/n_vclocks > +Date: May 2021 > +Contact: Yangbo Lu > +Description: > + This file contains the ptp virtual clocks number in use, > + based on current ptp physical clock. In default, the > + value is 0 meaning only ptp physical clock is in use. > + Setting the value can create corresponding number of ptp > + virtual clocks to use. But current ptp physical clock is > + guaranteed to stay free running. Setting the value back > + to 0 can delete ptp virtual clocks and back use ptp > + physical clock again. The native speaker in me suggests: This file contains the number of virtual PTP clocks in use. By default, the value is 0 meaning that only the physical clock is in use. Setting the value creates the corresponding number of virtual clocks and causes the physical clock to become free running. Setting the value back to 0 deletes the virtual clocks and switches the physical clock back to normal, adjustable operation. Thanks, Richard