On Fri, 2017-03-17 at 14:16 +0100, Bastien Nocera wrote: > On Fri, 2017-03-17 at 02:13 +0000, Pandruvada, Srinivas wrote: > > > > On Thu, 2017-03-16 at 18:20 +0800, Song Hongyan wrote: > > > > > > As accelerometer sensor becomes more and more popular, there are > > > more > > > user scenarios have been developed, "Hinge" is a very important > > > usecase > > > which needs two accelerometer sensors to calculate the included > > > angle > > > of keyboard and screen. > > > In this case, two accelerometer sensors will be exposed. > > > Currently, > > > IIO interface hasn't other way to distinguish two sensors with > > > same > > > sensor type, except sensor name. So a new sensor name > > > "accel_2nd_3d" > > > is added for secondary accelerometer sensor. > > > > This type of interface will not satisfy all cases. We have some > > hubs > > with many accelerometers attached. Same case is also true even for > > discrete sensors. So there should be some framework way to expose > > location of sensors. > > So you're nacking as well? Yes. > > > > > ACPI has special method called _PLD (Physical Device Location), > > which > > can be used to specify location of any device. So we need to be > > able > > to export such information to user space. We can add for each > > sensor > > the location information. > > > > I can propose some ABI for exporting location information. > > There were patches floating around to do this, but they were never > finished: > http://www.spinics.net/lists/linux-acpi/msg51540.html We need to add some of those element related to sensors to IIO ABI. I will propose an ABI as Jonathan suggested. Thanks, Srinivas ��.n��������+%������w��{.n�����{��)��^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
