Message-ID: <4ae6feff-147e-3148-cde4-53039c96ea80@wirenboard.com>
Date:   Sun, 12 Mar 2023 13:19:52 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.1
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
References: <20230301142835.19614-1-m.zatovic1@gmail.com>
Subject: Re: [PATCHv3 0/4] Wiegand bus driver and GPIO bitbanged controller
Content-Language: en-GB
From:   Evgeny Boger <boger@wirenboard.com>
Organization: Wiren Board
In-Reply-To: <20230301142835.19614-1-m.zatovic1@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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