Message ID | 20190608120443.21889-1-olteanv@gmail.com |
---|---|
Headers | show
Return-Path: <netdev-owner@vger.kernel.org> X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=<UNKNOWN>) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="n7p8rQIR"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 45LdSK0JfNz9s9y for <patchwork-incoming-netdev@ozlabs.org>; Sat, 8 Jun 2019 22:07:29 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727316AbfFHMFh (ORCPT <rfc822;patchwork-incoming-netdev@ozlabs.org>); Sat, 8 Jun 2019 08:05:37 -0400 Received: from mail-wr1-f65.google.com ([209.85.221.65]:42669 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726883AbfFHMFg (ORCPT <rfc822;netdev@vger.kernel.org>); Sat, 8 Jun 2019 08:05:36 -0400 Received: by mail-wr1-f65.google.com with SMTP id x17so4637631wrl.9; Sat, 08 Jun 2019 05:05:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id; bh=33BZqFnryBBp4WNaTRqIzVCwzWCs5N7VupVpVJEfc6Q=; b=n7p8rQIRljbFbpZc2OJQDih1YAFyFWu6/QfhvKvL200uwLNA5qx/RZr8GcZVidjniZ PQxe8VcG5GYmzfKsQFWquabFogiJ2wXKfSgTyAPwRKkmSrZEEDE/yj92xADsrPU3zte6 E2BZK2JORXfCfN/Fmao2yuuBqhtMeLQfg3q+xI258l7PRVtCKPUo0gMkyXLAzlrnR5df yfLpBo/lvzkdy131xOQ9VBP5T6ve4ycJzpROavNq3z5H1SAZGcCKapmzUgufqBMYeevg v2UANWk74Qir+BV54hqoqWMS3gw7Py+qffacZDPJgpomyXGLzCWCZGlmru6wxlBOb49d SOcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=33BZqFnryBBp4WNaTRqIzVCwzWCs5N7VupVpVJEfc6Q=; b=YvgbJhQctqKN1S3M8h4fkXKL33l2s+OzF/qr1VOkNT528tEtlrWQz07IOItBXLACZ8 8Zivcn5/m85xH0sEyQjFpnGPCKH9uYrBqEz2ih+6n5mf71pDZhSP1RZAJz29i8ZovlL7 r7jKHukxwwGrOkLPccZBSN+45of91pVky54HDeys/barSFDZV0vjEidjoejaa/Sd9q8v nl5+akOlh+hY9NLI5PILCJutNVpo/jxA6avBgBanjTBOZ0uR/h7sh7ux84Fz7NZgXlh8 5P6xNyZQUIZNnciaNZiI93UDPyZSxwFZj/ObCgzb0aRDpIWqtzfDxoYiMSmKSaAgBe2G mAPw== X-Gm-Message-State: APjAAAXmvTU4OzxnYuOo/VKoQ+2LpZX2A7Fz6ag7TvogpDioB0El+cBZ AxxYWTcp6NjdeBjuUThVSp0= X-Google-Smtp-Source: APXvYqxTXQUkS6gZyVPbfSZbLSJI9NfjGTBchPVapWqm2RCXOQqaePVN2ms8W614Tsi34Is5weFkZw== X-Received: by 2002:adf:de8b:: with SMTP id w11mr13434792wrl.134.1559995534381; Sat, 08 Jun 2019 05:05:34 -0700 (PDT) Received: from localhost.localdomain ([188.26.252.192]) by smtp.gmail.com with ESMTPSA id j16sm5440030wre.94.2019.06.08.05.05.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Jun 2019 05:05:33 -0700 (PDT) From: Vladimir Oltean <olteanv@gmail.com> To: f.fainelli@gmail.com, vivien.didelot@gmail.com, andrew@lunn.ch, davem@davemloft.net, richardcochran@gmail.com, john.stultz@linaro.org, tglx@linutronix.de, sboyd@kernel.org Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com> Subject: [PATCH v4 net-next 00/17] PTP support for the SJA1105 DSA driver Date: Sat, 8 Jun 2019 15:04:26 +0300 Message-Id: <20190608120443.21889-1-olteanv@gmail.com> X-Mailer: git-send-email 2.17.1 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: <netdev.vger.kernel.org> X-Mailing-List: netdev@vger.kernel.org |
Series |
PTP support for the SJA1105 DSA driver
|
expand
|
From: Vladimir Oltean <olteanv@gmail.com> Date: Sat, 8 Jun 2019 15:04:26 +0300 > This patchset adds the following: > > - A timecounter/cyclecounter based PHC for the free-running > timestamping clock of this switch. > > - A state machine implemented in the DSA tagger for SJA1105, which > keeps track of metadata follow-up Ethernet frames (the switch's way > of transmitting RX timestamps). > > Clock manipulations on the actual hardware PTP clock will have to be > implemented anyway, for the TTEthernet block and the time-based ingress > policer. Series applied, let's see how the build goes this time :-) Thanks.