Linux IIO development
 help / color / mirror / Atom feed
From: Michael Hennerich <michael.hennerich@analog.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	Drivers <Drivers@analog.com>,
	Guenter Roeck <guenter.roeck@ericsson.com>,
	Jean Delvare <khali@linux-fr.org>
Subject: Re: Oddities and how to handle them.
Date: Thu, 28 Apr 2011 12:04:10 +0200	[thread overview]
Message-ID: <4DB93B9A.6050500@analog.com> (raw)
In-Reply-To: <4DB933E3.8070803@cam.ac.uk>

On 04/28/2011 11:31 AM, Jonathan Cameron wrote:
> Guenter / Jean - cc'd you two because we have an sysfs interface naming question for
> AC sensors that touches on the edge of hwmon.
>
>   
>>>>>>> Hi Michael,
>>>>>>>
>>>>>>> ade7758 - Complex driver I'm not that keen on touching without a lot
>>>>>>> of testing support. Don't suppose you want to take this one Michael?
>>>>>>> (*looks hopeful*) At lease blugeoning it into more or less current
>>>>>>> interfaces would be a great help. I can do it, but then I suspect
>>>>>>> I'll break it in a few exciting ways :(
>>>>>>>
>>>>>>>               
>>>>>> I can fix building on this one. However I currently don't have
>>>>>> enough time to fix and document the API.
>>>>>>             
>>>>> That's fine.  We won't be pushing any of the energy meter drivers out
>>>>> of staging for a while yet anyway!
>>>>>           
>>>>>> The buffer scan attribute naming is a bit complicated on this one.
>>>>>> Do you think we can stick with wform?
>>>>>> There is some interaction with the WAVEFORM MODE Register. Ideally
>>>>>> we have enable files for all possible waveform selection
>>>>>> possibilities, which are numerous, 3 sources (phases)  * 5
>>>>>> measurement options (Current, Voltage, Active Power, Reactive
>>>>>> Power and VA). Only one combination can be enabled at a given
>>>>>> time, since they are exclusive
>>>>>>             
>>>>> or.
>>>>>           
>> Hi Jonathan,
>>
>> For the metering parts I think we need to define a few more channel types.
>>
>> How about this ones
>>
>> inSX            S is the apparent power.
>> inPX            P is the active power.
>> inQX            Q is the reactive power.
>> inVX            V is the voltage. (only inX ?)
>> inVRMSX VRMS is the quadratic mean voltage.
>>     
> Call it 'root mean square' rather than quadratic in the docs. They have different
> meanings in English.
>   
>> inIX            I is the current.
>>     
> currX as per hwmon?  They also define a power attribute, but only 1 (as DC
> I guess). Cc'd Guenter and Jean to see if we can / want to share an interface...
>   
Honestly I don't like 'curr' - In my opinion we should use SI until
symbols (as well as standardized derived SI units where applicable).
In this particular case current is a SI unit.
For everything further we should use symbols commonly used in
Anglo-American EE and Physics literature. (NIST, IEEE, ...)
 
> Guenter/ Jean, do you think hwmon will ever handle AC sensors? Maybe we want to be
> well clear of your interfaces just to avoid confusion? Or define a new set of shared
> names for the above that we will both use (when it becomes relevant?)
>   
>> inIRMSX IRMS is the quadratic mean current.
>>
>> Since they won't be really popular
>>
>> How about using a string in iio_chan_type_name_spec
>>
>>         [IIO_IN_GENERIC] = "in%s",
>>     
> Firstly, perhaps, IIO_IN_MOD will correspond better with naming?
>   
> Been thinking about exactly this question for the light sensors...
> Initially strings seemed like the obvious thing to do, but then I thought
> some more.  For all of these we will need to have matching event codes.
> The easiest there would be to do them as IIO_EV_MOD_POWER_APPARENT etc.
> Once we have those defines, we might as well roll the names into the core
> as a string table referenced by value stored in channel2.
> Actually, arguably we shouldn't be doing the same for 'x','y','z' as well
> for consistency. Right now we allow for directions without corresponding event
> codes. That way lies doom!
>
> I know there aren't likely to be hundreds of these devices any time soon,
> but we don't really want to set a precedence for allowing free naming.
> That was part of the justification for moving to chan_spec in the first
> place!
>
> Jonathan
>
>   


-- 
Greetings,
Michael

--
Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif

  reply	other threads:[~2011-04-28 10:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 16:13 Oddities and how to handle them Jonathan Cameron
2011-04-27 11:32 ` Michael Hennerich
2011-04-27 14:42   ` Jonathan Cameron
2011-04-27 15:03     ` Hennerich, Michael
2011-04-27 15:11       ` Jonathan Cameron
2011-04-28  8:36         ` Hennerich, Michael
2011-04-28  9:31           ` Jonathan Cameron
2011-04-28 10:04             ` Michael Hennerich [this message]
2011-04-28 10:19               ` Jonathan Cameron
2011-04-28 13:49                 ` Guenter Roeck
2011-04-28 13:51             ` Jean Delvare
2011-04-28 14:21               ` Jonathan Cameron
2011-04-28 14:23                 ` Guenter Roeck
2011-04-28 14:35                   ` Jonathan Cameron
2011-04-28 14:58                 ` [Device-drivers-devel] " Michael Hennerich
2011-04-28 15:46                   ` Jonathan Cameron
2011-04-29 14:21                     ` Michael Hennerich
2011-04-29 15:03                       ` Jonathan Cameron
2011-05-02  8:02                         ` Michael Hennerich
2011-05-02 14:50                           ` Jonathan Cameron
2011-05-03  9:26                             ` Michael Hennerich
2011-05-03  9:46                               ` Jonathan Cameron
2011-05-03 18:07                                 ` Jonathan Cameron
2011-05-04 10:56                                   ` Jonathan Cameron
2011-05-04 18:45                                     ` Hennerich, Michael

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=4DB93B9A.6050500@analog.com \
    --to=michael.hennerich@analog.com \
    --cc=Drivers@analog.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=guenter.roeck@ericsson.com \
    --cc=jic23@cam.ac.uk \
    --cc=khali@linux-fr.org \
    --cc=linux-iio@vger.kernel.org \
    /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