From: Michal Simek <michal.simek@xilinx.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, linux@roeck-us.net
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
"Colin Ian King" <colin.king@canonical.com>,
linux-iio@vger.kernel.org,
"Stefan Brüns" <stefan.bruens@rwth-aachen.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jean Delvare" <jdelvare@suse.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Hartmut Knaack" <knaack.h@gmx.de>
Subject: [PATCH 0/4] iio: adc: ina2xx: Improve device identification
Date: Tue, 20 Aug 2019 16:11:37 +0200 [thread overview]
Message-ID: <cover.1566310292.git.michal.simek@xilinx.com> (raw)
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
next reply other threads:[~2019-08-20 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 14:11 Michal Simek [this message]
2019-08-20 14:11 ` [PATCH 3/4] dt-bindings: Add optional label property for ina2xx Michal Simek
2019-08-27 17:06 ` Rob Herring
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=cover.1566310292.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=monstr@monstr.eu \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=stefan.bruens@rwth-aachen.de \
/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;
as well as URLs for NNTP newsgroup(s).