aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests
diff options
context:
space:
mode:
authorRichard Cochran <richardcochran@gmail.com>2020-03-29 07:55:10 -0700
committerDavid S. Miller <davem@davemloft.net>2020-03-30 11:16:38 -0700
commit62582a7ee78364c6106d09d5e0f1dc7f564be887 (patch)
tree8f5a378d3400230d67c45f57bee9a14e838380cc /tools/testing/selftests
parentnet: devlink: use NL_SET_ERR_MSG_MOD instead of NL_SET_ERR_MSG (diff)
downloadlinux-dev-62582a7ee78364c6106d09d5e0f1dc7f564be887.tar.xz
linux-dev-62582a7ee78364c6106d09d5e0f1dc7f564be887.zip
ptp: Avoid deadlocks in the programmable pin code.
The PTP Hardware Clock (PHC) subsystem offers an API for configuring programmable pins. User space sets or gets the settings using ioctls, and drivers verify dialed settings via a callback. Drivers may also query pin settings by calling the ptp_find_pin() method. Although the core subsystem protects concurrent access to the pin settings, the implementation places illogical restrictions on how drivers may call ptp_find_pin(). When enabling an auxiliary function via the .enable(on=1) callback, drivers may invoke the pin finding method, but when disabling with .enable(on=0) drivers are not permitted to do so. With the exception of the mv88e6xxx, all of the PHC drivers do respect this restriction, but still the locking pattern is both confusing and unnecessary. This patch changes the locking implementation to allow PHC drivers to freely call ptp_find_pin() from their .enable() and .verify() callbacks. V2 ChangeLog: - fixed spelling in the kernel doc - add Vladimir's tested by tag Signed-off-by: Richard Cochran <richardcochran@gmail.com> Reported-by: Yangbo Lu <yangbo.lu@nxp.com> Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests')
0 files changed, 0 insertions, 0 deletions