All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio <linux-gpio@vger.kernel.org>, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH 1/3 v5] gpio: pcf857x: Name instance after dev_name()
Date: Fri, 25 Jun 2021 01:52:38 +0200	[thread overview]
Message-ID: <CACRpkdZwcd8jznvzEvzO0rmF7ug3o_TxC=xUeCPYgfhg00rEQQ@mail.gmail.com> (raw)
In-Reply-To: <CAMpxmJXqGgPiXqR1kq+nts-=HBkxSP_7Cqzn=N5-EmKWADh0CQ@mail.gmail.com>

On Tue, Jun 22, 2021 at 2:58 PM Bartosz Golaszewski
<bgolaszewski@baylibre.com> wrote:

> This makes sense but the i2c names are often not very descriptive. How
> about adding a DEVID_AUTO/DEVID_NONE like mechanism to GPIO labels?
> Nvmem has a thing like that precisely because labels can repeat.

Yeah :/ it feels like the subsystem should name the device properly
though. Like we're solving someone elses problem.

In this case the other patches provides .names in the I2C
board info so that the dev_name() ends up something
like "i2c-u2" and "i2c-u15". The u2 and u15 are common
names for components on a board so from an electronic point
of view that naming makes for good topology.

Yours,
Linus Walleij

  reply	other threads:[~2021-06-24 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 14:59 [PATCH 1/3 v5] gpio: pcf857x: Name instance after dev_name() Linus Walleij
2021-06-15 14:59 ` [PATCH 2/3 v5] ARM: davinci: dm644x: Convert LEDs to GPIO descriptor table Linus Walleij
2021-06-15 14:59 ` [PATCH 3/3 v5] ARM: davinci: dm646x: " Linus Walleij
2021-06-22 12:58 ` [PATCH 1/3 v5] gpio: pcf857x: Name instance after dev_name() Bartosz Golaszewski
2021-06-24 23:52   ` Linus Walleij [this message]
2021-06-25 10:25     ` Bartosz Golaszewski

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='CACRpkdZwcd8jznvzEvzO0rmF7ug3o_TxC=xUeCPYgfhg00rEQQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=nsekhar@ti.com \
    /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.