From: Evgeny Boger <boger@wirenboard.com>
To: m.zatovic1@gmail.com
Cc: airlied@redhat.com, andriy.shevchenko@intel.com, arnd@arndb.de,
axboe@kernel.dk, benjamin.tissoires@redhat.com,
bvanassche@acm.org, dan.j.williams@intel.com,
devicetree@vger.kernel.org, dipenp@nvidia.com,
fmdefrancesco@gmail.com, furong.zhou@linux.intel.com,
gregkh@linuxfoundation.org, jacek.lawrynowicz@linux.intel.com,
krzysztof.kozlowski+dt@linaro.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, linux@zary.sk,
masahiroy@kernel.org, mathieu.poirier@linaro.org,
mwen@igalia.com, ogabbay@kernel.org, robh+dt@kernel.org,
treding@nvidia.com, yangyicong@hisilicon.com
Subject: Re: [PATCHv3 0/4] Wiegand bus driver and GPIO bitbanged controller
Date: Sun, 12 Mar 2023 13:19:52 +0300 [thread overview]
Message-ID: <4ae6feff-147e-3148-cde4-53039c96ea80@wirenboard.com> (raw)
In-Reply-To: <20230301142835.19614-1-m.zatovic1@gmail.com>
Hi Martin,
Thank you for you work! I'm currently working on Wiegand *receiver*
kernel driver, and hopefully we can make both sending and receiving
Wiegand implementation in kernel.
I tried to read all the discussion for the previous series, but still
don't quite understand why do we need the infrastructure to be that
complex. I mean Wiegand is point-to-point connection, so why do we even
need bus/controller/device abstractions at all? There will be always
just the single device per controller, right?
--
Kind regards,
Evgeny Boger
CTO @ Wiren Board
prev parent reply other threads:[~2023-03-12 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 14:28 Martin Zaťovič
2023-03-01 14:28 ` [PATCHv3 1/4] dt-bindings: wiegand: add Wiegand controller common properties Martin Zaťovič
2023-03-03 19:32 ` Rob Herring
2023-03-01 14:28 ` [PATCHv3 2/4] wiegand: add Wiegand bus driver Martin Zaťovič
2023-03-01 16:23 ` Andy Shevchenko
2023-03-01 16:48 ` Andy Shevchenko
2023-04-04 13:13 ` Martin Zaťovič
2023-04-04 20:30 ` Linus Walleij
2023-04-05 8:39 ` Andy Shevchenko
2023-03-01 22:53 ` kernel test robot
[not found] ` <CAPGNi97oc+tSrt-NF4KZhcEyUfZTo4PT0ms8zYSFVEyzOBq4ZA@mail.gmail.com>
2023-03-14 15:15 ` Andy Shevchenko
2023-03-01 14:28 ` [PATCHv3 3/4] dt-bindings: wiegand: add GPIO bitbanged Wiegand controller Martin Zaťovič
2023-03-12 10:34 ` Evgeny Boger
2023-03-01 14:28 ` [PATCHv3 4/4] wiegand: add Wiegand GPIO bitbanged controller driver Martin Zaťovič
2023-03-01 16:43 ` Andy Shevchenko
2023-03-02 2:11 ` kernel test robot
2023-03-12 10:32 ` Evgeny Boger
2023-03-01 16:43 ` [PATCHv3 0/4] Wiegand bus driver and GPIO bitbanged controller Andy Shevchenko
2023-03-12 10:19 ` Evgeny Boger [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=4ae6feff-147e-3148-cde4-53039c96ea80@wirenboard.com \
--to=boger@wirenboard.com \
--cc=airlied@redhat.com \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=benjamin.tissoires@redhat.com \
--cc=bvanassche@acm.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dipenp@nvidia.com \
--cc=fmdefrancesco@gmail.com \
--cc=furong.zhou@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
--cc=m.zatovic1@gmail.com \
--cc=masahiroy@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mwen@igalia.com \
--cc=ogabbay@kernel.org \
--cc=robh+dt@kernel.org \
--cc=treding@nvidia.com \
--cc=yangyicong@hisilicon.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 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®