Re: [PATCH net-next 3/3] ptp: derive the device name from the parent device
From: Richard Cochran <richardcochran@gmail.com>
Date: 2012-09-21 18:40:47
On Fri, Sep 21, 2012 at 07:23:03PM +0100, Ben Hutchings wrote:
I think what I'm still missing from you is some explanation of what the 'clock name' is meant to be used as - a type name, a unique identifier, a 'friendly name' for listing clocks in a user interface?
The original idea was a type/friendly kind of thing. Imagine you are the admin of some random box that should run PTP. You do 'cat /sys/class/ptp/ptp0/clock_name' and see "gianfar clock". Then you think to yourself, "Excellent, I know that one, it works great, and I can even get a PPS output." But if you saw "IXP46X timer" then you would think, "Forget it, this will never work." That was the idea. But before the ethtool thing came along, people started putting MAC addresses in that string, and it continued even after the ethtool method appeared. I wanted to correct the MAC abuses, but then I thought you were concurring with putting some kind of semi-unique device ID there. I really don't care too much about the clock_name anyhow, because I always know my own hardware. I don't mind changing it from type-string or friendly-name to device ID, if people think that is more useful. Thanks, Richard