From: "Arnd Bergmann" <arnd@arndb.de>
To: "Martin Zaťovič" <m.zatovic1@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Manivannan Sadhasivam" <mani@kernel.org>,
hemantk@codeaurora.org, quic_jhugo@quicinc.com,
"Bjorn Andersson" <andersson@kernel.org>,
Michael.Srba@seznam.cz, dipenp@nvidia.com,
"Bart Van Assche" <bvanassche@acm.org>,
iwona.winiarska@intel.com, "Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
fmdefrancesco@gmail.com, jason.m.bills@linux.intel.com,
jae.hyun.yoo@linux.intel.com, krzysztof.kozlowski+dt@linaro.org,
"Rob Herring" <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] bus: add Wiegand bus driver
Date: Wed, 25 Jan 2023 14:16:05 +0100 [thread overview]
Message-ID: <43964d94-1c76-4c4f-b093-92a611518a87@app.fastmail.com> (raw)
In-Reply-To: <Y9EpNfZJ5irXZqvR@fedora>
On Wed, Jan 25, 2023, at 14:05, Martin Zaťovič wrote:
> Hello Greg,
>
> thank you for your insights! The static lists are needed
> for matching wiegand_board_info structures to
> wiegand_controller structures for drivers of devices that
> do not use devicetree. I have seen this approach in the
> SPI bus driver, so I assumed it was okay. If there is
> a better way, please let me know.
We have removed most of the support for machines that come
without devicetree, and it is unlikely that we will be merging
any new ones, so I expect this can simply be left out.
Are there any corner cases where you you still expect to
add devices manually from another driver?
Arnd
next prev parent reply other threads:[~2023-01-25 13:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 13:34 [PATCH 0/3] Wiegand bus driver and GPIO controller driver Martin Zaťovič
2023-01-04 13:34 ` [PATCH 1/3] dt-bindings: add Wiegand controller dt-binding documentation Martin Zaťovič
2023-01-05 2:53 ` Rob Herring
2023-01-05 2:53 ` Rob Herring
2023-01-08 16:30 ` Rob Herring
2023-01-22 14:21 ` Krzysztof Kozlowski
2023-01-04 13:34 ` [PATCH 2/3] bus: add Wiegand bus driver Martin Zaťovič
2023-01-04 14:03 ` Greg KH
2023-01-04 14:05 ` Greg KH
2023-01-25 13:05 ` Martin Zaťovič
2023-01-25 13:16 ` Arnd Bergmann [this message]
2023-01-25 13:21 ` Martin Zaťovič
2023-01-25 13:26 ` Greg KH
2023-01-25 13:37 ` Martin Zaťovič
2023-01-04 14:06 ` Greg KH
2023-01-04 13:34 ` [PATCH 3/3] wiegand: add Wiegand GPIO bit-banged controller driver Martin Zaťovič
2023-01-04 14:05 ` Greg KH
2023-01-04 16:39 ` kernel test robot
2023-01-04 16:59 ` Andy Shevchenko
2023-01-04 17:01 ` Andy Shevchenko
2023-01-25 9:28 ` Martin Zaťovič
2023-01-25 11:49 ` Andy Shevchenko
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=43964d94-1c76-4c4f-b093-92a611518a87@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Michael.Srba@seznam.cz \
--cc=andersson@kernel.org \
--cc=bvanassche@acm.org \
--cc=devicetree@vger.kernel.org \
--cc=dipenp@nvidia.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=iwona.winiarska@intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jason.m.bills@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.zatovic1@gmail.com \
--cc=mani@kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®