From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-182.mta1.migadu.com (out-182.mta1.migadu.com [95.215.58.182]) (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 4AAF0262FED for ; Sat, 29 Nov 2025 19:54:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764446051; cv=none; b=LgnQBp0qaEi1oi7HyPeTK9+VhX8aL/kCe7Snzbb76Wr7Tcjw6cxTB6B6XeuEKTkxSorDw1t7+87dZN9npHg7urmi+iIZmV8wVOYJizIxqOg+ZcBRvUw4QLKgt5AhUH5DSPe86aq4MDhnVmnLbrUpHwpY8hruJrjmijFfW2k+Wsk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764446051; c=relaxed/simple; bh=RnsyQk1wAhESAL9NZ6r7tQkFmlyPQfNHc0+oJKGgHHI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=LpX4sruEm2fBJkcLfHAFg9Shr0C/po4EsumrzUxJKD85Dtw25A8R1PbIR3TWIw0FnZxSSwTZMzVapLqzDphFl0qBUlqZKruj8DUlu3vOlwVS7ST+eesPuecaYzjEwieiaqw9XWgFBDAb528JLCGMPxjsUnjfrCeWFzNtVc/aBJI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=E7dSR+Af; arc=none smtp.client-ip=95.215.58.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="E7dSR+Af" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1764446042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=co0b32nW5KE2GchwbO7OZkvJYPLPhNkU8cwwV1mqcBg=; b=E7dSR+AfoIXHP/qHW8PxKl3jcFEFYrMq/LHzUqhcP4DId8LeBzy21C+uWUlfKfRXirdjct +6g9+b/qLHifNnmIyZGIUoSDwkYNbbfltBl2ZVGSMYZtQJU9TijKQsdySEOfPqkYWomyJq BuiCS5X8X1J7JZgj0imADFsgoYQJjO8= From: Vadim Fedorenko To: Andrew Lunn , Russell King , Heiner Kallweit , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Richard Cochran , Andrew Lunn Cc: Simon Horman , Vladimir Oltean , Jacob Keller , Kory Maincent , netdev@vger.kernel.org, Vadim Fedorenko Subject: [PATCH net-next v2 0/4] support for hwtstamp_get in phy - part 2 Date: Sat, 29 Nov 2025 19:53:30 +0000 Message-ID: <20251129195334.985464-1-vadim.fedorenko@linux.dev> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT There are 2 drivers which had some inconsistency in HW timestamping configuration logic. Improve both of them and add hwtstamp_get() callback. v1 -> v2: * add checks and return error in case of unsupported TX tiemstamps * get function for lan8814 and lan8841 are the same - keep only one Vadim Fedorenko (4): net: phy: micrel: improve HW timestamping config logic net: phy: micrel: add HW timestamp configuration reporting net: phy: microchip_rds_ptp: improve HW ts config logic net: phy: microchip_rds_ptp: add HW timestamp configuration reporting drivers/net/phy/micrel.c | 35 ++++++++++++++++++++++++----- drivers/net/phy/microchip_rds_ptp.c | 34 +++++++++++++++++++++++----- 2 files changed, 58 insertions(+), 11 deletions(-) -- 2.47.3