From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out30-97.freemail.mail.aliyun.com (out30-97.freemail.mail.aliyun.com [115.124.30.97]) (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 6935E23ABB9 for ; Mon, 9 Mar 2026 02:28:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.97 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773023315; cv=none; b=luSqWyZKoS1vgiIK7FQoAbuDKMgtp7o6GYl8q1Wev29+ysoHuZPbJtMstTINnLcTZrqhwBKEYFQkADZMEghyAZfW/itl+ZzMHq/ghSodSx9AP9gmwChnOg0oSTdZTcp3KRG9V0uww3Y/D6M2iaeHI/m0TbvqkO/Yrkzho/hSTZM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773023315; c=relaxed/simple; bh=9+7Gl9tuAZ1Q0VSNcuAVDQMPoA6ngxLTTu1pfkwf7ig=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=NkK2NNx6Ay1qSP8u1Ae0v32xP2lG2SaShBA7PqE0F87k6EDKEUmuQ9zWKcCRBHeEcS5Qz2njCUd7zY0YHzlv1LPfQwCvYQM3rkdOWNc0AW70ss80k/0nCk1FsC7A9EbyS+uLaGf7vwybALYL4e/hhxRry5u0+A0ER+ziXa+FH2o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=NlYjlLJF; arc=none smtp.client-ip=115.124.30.97 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="NlYjlLJF" DKIM-Signature:v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1773023305; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type; bh=qmhKuTU3gUKJMAVU5dtpO7oqXqxZXnfftl1UL5iMYm0=; b=NlYjlLJF0JPS2GiOOG6nAIb9XEeGmj3Pugsd95TgqKbjWsnwPKJh6jZrzSoMJVujyUcHEMg1mwb8CF6LsUyWmzI+imktExapM6byzCFlNfMcAsxHsrHXaQ3HUqnXTYcCdC7B0+mqAkbhIFuk57RcjXpAF3I95g0d05wqHHcF9EI= Received: from 30.221.130.175(mailfrom:guwen@linux.alibaba.com fp:SMTPD_---0X-TA9qB_1773023302 cluster:ay36) by smtp.aliyun-inc.com; Mon, 09 Mar 2026 10:28:23 +0800 Message-ID: <6397594f-eb3f-4207-9c20-b0f7e409054c@linux.alibaba.com> Date: Mon, 9 Mar 2026 10:28:21 +0800 Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership To: Jakub Kicinski Cc: David Woodhouse , tglx@kernel.org, tglx@linutronix.de, richardcochran@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com, pabeni@redhat.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, mani@kernel.org, imran.shaik@oss.qualcomm.com, vladimir.oltean@nxp.com, wei.fang@nxp.com, xiaoning.wang@nxp.com, jonathan.lemon@gmail.com, vadim.fedorenko@linux.dev, yangbo.lu@nxp.com, svens@linux.ibm.com, nick.shi@broadcom.com, ajay.kaher@broadcom.com, alexey.makhalov@broadcom.com, bcm-kernel-feedback-list@broadcom.com, linux-fpga@vger.kernel.org, imx@lists.linux.dev, linux-s390@vger.kernel.org, dust.li@linux.alibaba.com, xuanzhuo@linux.alibaba.com, taniya.das@oss.qualcomm.com References: <20260227081934.96865-1-guwen@linux.alibaba.com> <4a9af4b1-6820-4173-8daf-4201bb1bcca5@linux.alibaba.com> <20260305184110.13e79837@kernel.org> From: Wen Gu In-Reply-To: <20260305184110.13e79837@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2026/3/6 10:41, Jakub Kicinski wrote: > On Fri, 27 Feb 2026 20:25:11 +0800 Wen Gu wrote: >> As mentioned in RFC v1, the use cases for drivers in the emulated PHC category >> are expected to be quite diverse, and not limited to the virtualization/guest >> time sync use case. For example, existing drivers such as ptp_ocp [1] and >> upcoming ones such as mhi_phc [2] are not related to virtualization use cases. > > ptp_ocp is a real PCIe device with an atomic clock. mhi_phc is some > qualcomm fw-defined thing, so more closely mapping what you're doing. > ptp_ocp should probably stay under netdev, we maintain DPLL drivers, > too. Main thing we/I don't want to deal with is all the corporate NIH > virtualization excreta. OK. ptp_ocp will be kept under netdev in the next version.