All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Reid <preid@electromag.com.au>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, robh+dt@kernel.org, mark.rutland@arm.com,
	preid@electromag.com.au, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, michal.simek@xilinx.com
Subject: [PATCH v2 0/2] iio: core: Add optional symbolic label to device attributes
Date: Thu, 19 Sep 2019 22:36:06 +0800	[thread overview]
Message-ID: <1568903768-65998-1-git-send-email-preid@electromag.com.au> (raw)

If a label is defined in the device tree for this device add that
to the device specific attributes. This is useful for userspace to
be able to identify an individual device when multiple identical
chips are present in the system.

Similar to leds, display labels etc.

Changes from V1:
- Update commit message for dt_bind commit
- Update example label for dt-binding

I haven't added Rob's reviewed-by from V1. Wasnt't
sure if the changes are minor enough to keep that.

Phil Reid (2):
  dt-binding: iio: Add optional label property
  iio: core: Add optional symbolic label to device attributes

 Documentation/devicetree/bindings/iio/iio-bindings.txt |  5 +++++
 drivers/iio/industrialio-core.c                        | 17 +++++++++++++++++
 include/linux/iio/iio.h                                |  1 +
 3 files changed, 23 insertions(+)

-- 
1.8.3.1


             reply	other threads:[~2019-09-19 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 14:36 Phil Reid [this message]
2019-09-19 14:36 ` [PATCH v2 1/2] dt-binding: iio: Add optional label property Phil Reid
2019-09-27 14:44   ` Rob Herring
2019-10-05 14:58     ` Jonathan Cameron
2019-09-19 14:36 ` [PATCH v2 2/2] iio: core: Add optional symbolic label to device attributes Phil Reid
2019-10-05 14:59   ` Jonathan Cameron
2019-10-07 20:32     ` Jonathan Cameron
2019-10-08  7:06       ` Phil Reid
2019-10-08 12:40         ` Jonathan Cameron

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=1568903768-65998-1-git-send-email-preid@electromag.com.au \
    --to=preid@electromag.com.au \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.