From: Richard Cochran <richardcochran@gmail.com>
To: <netdev@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Ben Hutchings" <ben@decadent.org.uk>,
"Christian Riesch" <christian.riesch@omicron.at>,
"David Miller" <davem@davemloft.net>,
"Stefan Sørensen" <stefan.sorensen@spectralink.com>
Subject: [PATCH net-next v3 0/9] ptp: dynamic pin control
Date: Thu, 20 Mar 2014 22:21:51 +0100 [thread overview]
Message-ID: <cover.1395350105.git.richardcochran@gmail.com> (raw)
This patch series introduces a way of changing the auxiliary PTP
Hardware Clock functions (periodic output signals and time stamping
external signals) at run time. In the past on the netdev list, we have
discussed other ways to handle this, such as module parameters and
ethtool. This series implements a new PHC ioctl because that is the
most natural way. Users already activate the auxiliary functions via
the ioctls. The sysfs interface has also been expanded so that the pin
configuration can be programmed using shell scripts.
The first patch adds the new ioctls. The PHC subsystem does most of
the work of maintaining the function-to-pin mapping. Drivers will only
need to allocate and initialize a pin configuration table and also
provide a new method that validates a particular assignment.
Patches 5 and 6 just clean up a couple of issues in the phyter driver,
and the remaining patches actually hook the phyter's pins into the new
system.
Comments and questions are most welcome.
Thanks,
Richard
* ChangeLog
** V3
- simplify locking in the set pin logic
** V2
- fix bug in sysfs code on init error path
- rename ptp_setpin() to ptp_set_pinfunc()
- rename .setpin() to .verify() in the driver interface
- simplify ptp_find_pin() logic
- use correct test when checking whether the pin with the
calibration function is being reprogrammed
Richard Cochran (9):
ptp: introduce programmable pins.
ptp: add the pin GET/SETFUNC ioctls to the testptp program.
ptp: expose the programmable pins via sysfs
ptp: drivers: set the number of programmable pins.
dp83640: trivial fixes
dp83640: correct the periodic output frequency
dp83640: implement programmable pin functions.
dp83640: let external input pins from the module parameters be
defaults.
dp83640: let the periodic pin from the module parameter be a default.
Documentation/ABI/testing/sysfs-ptp | 20 ++++
Documentation/ptp/testptp.c | 58 +++++++++-
drivers/net/ethernet/adi/bfin_mac.c | 1 +
drivers/net/ethernet/broadcom/tg3.c | 1 +
drivers/net/ethernet/freescale/fec_ptp.c | 1 +
drivers/net/ethernet/freescale/gianfar_ptp.c | 1 +
drivers/net/ethernet/intel/e1000e/ptp.c | 1 +
drivers/net/ethernet/mellanox/mlx4/en_clock.c | 1 +
drivers/net/ethernet/sfc/ptp.c | 1 +
drivers/net/ethernet/stmicro/stmmac/stmmac_ptp.c | 1 +
drivers/net/ethernet/ti/cpts.c | 1 +
drivers/net/ethernet/tile/tilegx.c | 1 +
drivers/net/phy/dp83640.c | 93 +++++++++++++---
drivers/ptp/ptp_chardev.c | 128 +++++++++++++++++++++-
drivers/ptp/ptp_clock.c | 23 ++++
drivers/ptp/ptp_ixp46x.c | 1 +
drivers/ptp/ptp_pch.c | 1 +
drivers/ptp/ptp_private.h | 8 ++
drivers/ptp/ptp_sysfs.c | 115 +++++++++++++++++++
include/linux/ptp_clock_kernel.h | 33 ++++++
include/uapi/linux/ptp_clock.h | 39 ++++++-
21 files changed, 509 insertions(+), 20 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-03-20 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 21:21 Richard Cochran [this message]
2014-03-20 21:21 ` [PATCH net-next v3 1/9] ptp: introduce programmable pins Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 2/9] ptp: add the pin GET/SETFUNC ioctls to the testptp program Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 3/9] ptp: expose the programmable pins via sysfs Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 4/9] ptp: drivers: set the number of programmable pins Richard Cochran
2014-03-21 8:02 ` Jeff Kirsher
2014-03-20 21:21 ` [PATCH net-next v3 5/9] dp83640: trivial fixes Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 6/9] dp83640: correct the periodic output frequency Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 7/9] dp83640: implement programmable pin functions Richard Cochran
2014-03-20 21:21 ` [PATCH net-next v3 8/9] dp83640: let external input pins from the module parameters be defaults Richard Cochran
2014-03-20 21:22 ` [PATCH net-next v3 9/9] dp83640: let the periodic pin from the module parameter be a default Richard Cochran
2014-03-21 18:22 ` [PATCH net-next v3 0/9] ptp: dynamic pin control David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1395350105.git.richardcochran@gmail.com \
--to=richardcochran@gmail.com \
--cc=ben@decadent.org.uk \
--cc=christian.riesch@omicron.at \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan.sorensen@spectralink.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).