From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Bamvor Jian Zhang <bamv2005@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
kernel <kernel@axis.com>, devicetree <devicetree@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<robh+dt@kernel.org>
Subject: Re: [PATCH v2] gpio: mockup: Allow probing from device tree
Date: Wed, 28 Oct 2020 12:52:03 +0100 [thread overview]
Message-ID: <20201028115203.qy7nu6bn7dy77vzm@axis.com> (raw)
In-Reply-To: <CAHp75Vcy-m6tT3ChPYQ8vvsAOwV4CUM3feewb5bpk8h7mqa+AA@mail.gmail.com>
On Wed, Oct 28, 2020 at 12:43:22PM +0100, Andy Shevchenko wrote:
> On Wed, Oct 28, 2020 at 10:00 AM Vincent Whitchurch
> <vincent.whitchurch@axis.com> wrote:
> > Allow the mockup driver to be probed via the device tree without any
> > module parameters, allowing it to be used to configure and test higher
> > level drivers like the leds-gpio driver and corresponding userspace
> > before actual hardware is available.
>
> You have to officially announce a DT binding for that.
Rob Herring has earlier said that was not required for this driver. As
I mentioned a little further down in the email you are replying to:
| Drop DT binding document, since Rob Herring was OK with not documenting
| this:
| https://lore.kernel.org/linux-devicetree/5baa1ae6.1c69fb81.847f2.3ab1@mx.google.com/
prev parent reply other threads:[~2020-10-28 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 13:53 Vincent Whitchurch
2020-10-27 18:12 ` Bartosz Golaszewski
2020-10-28 8:57 ` Vincent Whitchurch
2020-10-28 20:25 ` Andy Shevchenko
2020-10-28 20:26 ` Andy Shevchenko
2020-10-29 7:54 ` Vincent Whitchurch
2020-10-29 9:30 ` Bartosz Golaszewski
2020-10-28 11:43 ` Andy Shevchenko
2020-10-28 11:52 ` Vincent Whitchurch [this message]
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=20201028115203.qy7nu6bn7dy77vzm@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=andy.shevchenko@gmail.com \
--cc=bamv2005@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®