Messages in this thread | | | Date | Mon, 4 Jan 2021 11:48:42 -0800 | From | Jakub Kicinski <> | Subject | Re: [PATCH net-next] nfc: Add a virtual nci device driver |
| |
On Thu, 31 Dec 2020 14:22:45 +0900 Bongsu Jeon wrote: > On Tue, Dec 29, 2020 at 6:16 AM Jakub Kicinski <kuba@kernel.org> wrote: > > > > On Mon, 28 Dec 2020 18:45:07 +0900 Bongsu Jeon wrote: > > > From: Bongsu Jeon <bongsu.jeon@samsung.com> > > > > > > A NCI virtual device can be made to simulate a NCI device in user space. > > > Using the virtual NCI device, The NCI module and application can be > > > validated. This driver supports to communicate between the virtual NCI > > > device and NCI module. > > > > > > Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com> > > > > net-next is still closed: > > > > http://vger.kernel.org/~davem/net-next.html > > > > Please repost in a few days. > > > > As far as the patch goes - please include some tests for the NCI/NFC > > subsystem based on this virtual device, best if they live in tree under > > tools/testing/selftest. > > thank you for your answer. > I think that neard(NFC deamon) is necessary to test the NCI subsystem > meaningfully. > The NCI virtual device in user space can communicate with neard > through this driver. > Is it enough to make NCI virtual device at tools/nfc for some test?
I'm not sure if I understand. Are you asking if it's okay for the test or have a dependency on neard?
| |