[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1566310292.git.michal.simek@xilinx.com>
Date: Tue, 20 Aug 2019 16:11:37 +0200
From: Michal Simek <michal.simek@...inx.com>
To: linux-kernel@...r.kernel.org, monstr@...str.eu,
michal.simek@...inx.com, linux@...ck-us.net
Cc: linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
Colin Ian King <colin.king@...onical.com>,
linux-iio@...r.kernel.org,
Stefan BrĂ¼ns <stefan.bruens@...h-aachen.de>,
Rob Herring <robh+dt@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Jean Delvare <jdelvare@...e.com>,
Mark Rutland <mark.rutland@....com>,
Jonathan Cameron <jic23@...nel.org>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Hartmut Knaack <knaack.h@....de>
Subject: [PATCH 0/4] iio: adc: ina2xx: Improve device identification
Hi,
the purpose of this series is to improve ina226 identification. On systems
like Xilinx ZynqMP zcu102 (check dt in the tree) you can find out almost 20
ina226 chips and it is impossible to find out based on simple ina226 which
chip is repsonsible for what.
The series is adding two ways how to improve device identification.
Please let me know what you think I am happy to do changes in it.
Thanks,
Michal
Michal Simek (4):
iio: adc: ina2xx: Define *device_node only once
iio: adc: ina2xx: Setup better name then simple ina2xx
dt-bindings: Add optional label property for ina2xx
iio: adc: ina2xx: Use label proper for device identification
.../devicetree/bindings/hwmon/ina2xx.txt | 2 ++
drivers/iio/adc/ina2xx-adc.c | 15 +++++++++++----
2 files changed, 13 insertions(+), 4 deletions(-)
--
2.17.1
Powered by blists - more mailing lists