From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0020CC433ED for ; Thu, 13 May 2021 14:51:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C54CC61433 for ; Thu, 13 May 2021 14:51:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234612AbhEMOwa (ORCPT ); Thu, 13 May 2021 10:52:30 -0400 Received: from new4-smtp.messagingengine.com ([66.111.4.230]:53699 "EHLO new4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234592AbhEMOuJ (ORCPT ); Thu, 13 May 2021 10:50:09 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 3A9D0580715; Thu, 13 May 2021 10:48:58 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 13 May 2021 10:48:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=animalcreek.com; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=lEk17EktawF4yxbelteLRZPL1u7 6s2v81K0ba/CVsLk=; b=dst6D/19N83Ua2dTF3g8TngtqoC74H416i/EgnfFofw 3nDGfArAk0ihsOzFOXuI3Us9IQFYQ3uJIYjuS3vmZtIp7dMORyM203+z/PTZXGIm 0K6zTD7y6l2J5h/CKj9LatOU5HmHItaLeCljRBMLW8H50IObu6v7xN61hrQBlAun 6EZUSN+eJVy0uOIjrFmPbmTAOV9MFtNXMj3u33s2IbZ80DJyJ4iD/yn+/VW+Poi7 AX9+ztICVwZ1fvHg7sSypdr44GHSFY6g5w7oZV0FeWnBFqpvRnixHGvKYTlqQceD QWMFLua5JCumUiEuIfsK4aK4aunhJ25PvbdS2f8m63Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=lEk17E ktawF4yxbelteLRZPL1u76s2v81K0ba/CVsLk=; b=B+ppxc5KqjbyAI6jGMV0c8 l3rNFJ7Cuvtgmgbrcd2UqMszPUVD81ml/Z5DXib3PMsSrlyNMRuMkgVd1JP5YhDB hiLV16AtlCPMxN94/W0JHvpl5JzwyH+Jii5h0tTcAjl4JzOCsLtXan7dhBSVBBmt fuqC4rkbUeO7cOauaJuk+/vvkS3SGqGf+SgEK+dGpS2HXcyRUszpwXOlkbzl5kws i3Lb4v9fyJE4UWnkJJlI2yB2QwXpRk70NV+wzeXCWM+TrMpMr/tRnFf9+QrmPQqX pFVLmTp8O3lLVs+5VW/BKfBbTnShAWKcMx6tXDqlRv8ku56C1IWNr06O0BKVgkcA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdehgedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjohesthdtredttddtvdenucfhrhhomhepofgrrhhk ucfirhgvvghruceomhhgrhgvvghrsegrnhhimhgrlhgtrhgvvghkrdgtohhmqeenucggtf frrghtthgvrhhnpedujeelgeejleegleevkeekvdevudfhteeuiedtleehtdduleelvdei fffhvdehtdenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecukfhppeejtddrudejvd drfedvrddvudeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepmhhgrhgvvghrsegrnhhimhgrlhgtrhgvvghkrdgtohhm X-ME-Proxy: Received: from blue.animalcreek.com (ip70-172-32-218.ph.ph.cox.net [70.172.32.218]) by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 13 May 2021 10:48:56 -0400 (EDT) Received: by blue.animalcreek.com (Postfix, from userid 1000) id 8E0EF136008E; Thu, 13 May 2021 07:48:55 -0700 (MST) Date: Thu, 13 May 2021 07:48:55 -0700 From: Mark Greer To: Stephan Gerhold Cc: Mark Greer , Frieder Schrempf , Krzysztof Kozlowski , Jakub Kicinski , "David S. Miller" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfc@lists.01.org, Alex Blasche , phone-devel@vger.kernel.org Subject: Re: Testing wanted for Linux NFC subsystem Message-ID: <20210513144855.GA266838@animalcreek.com> References: <20210512144319.30852-1-krzysztof.kozlowski@canonical.com> <14e78a9a-ed1a-9d7d-b854-db6d811f4622@kontron.de> <20210512170135.GB222094@animalcreek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Animal Creek Technologies, Inc. Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 13, 2021 at 01:49:53PM +0200, Stephan Gerhold wrote: > Hi! Hi Stephan and thanks for stepping up. > I have a couple of "recycled" smartphones running mainline Linux > and some of them do have NFC chips. I have two with NXP PN547 > (supported by nxp,nxp-nci-i2c), one with Samsung S3FWRN5 > (samsung,s3fwrn5-i2c) and even one with Broadcom BCM2079x I think > (this one does not have a driver for the Linux NFC subsystem sadly). > > +Cc phone-devel@vger.kernel.org, in case other people there are > interested in NFC :) > > The NXP/Samsung ones seems to work just fine. However, since there are > barely any userspace tools making use of Linux NFC all my testing so far > was limited to polling for devices with "nfctool" and being happy enough > when it realizes that I hold some NFC tag close to the device. :S There is a user-level daemon that is the counterpart for the in-kernel NFC subsystem. It is called neard and is available here: git://git.kernel.org/pub/scm/network/nfc/neard.git There are a few test script in it that will let you read and write NFC tags, and do some other things. We can add some more tests to that set as we go. > I would be happy to do some more testing if someone has something useful > that can be tested. However, I guess ideally we would have someone who > actually uses Linux NFC actively for some real application. :) Ideally, you should have some NFC tags of various types. Types 2, 3, 4A, 4B, and 5 tags are supported. Peer-to-peer mode is supported too so you should be able to transfer data from one of your phones to the other over NFC (and do a BT hand-over, if you're interested). Note that the specified range for NFC is only 4 cm and poor antenna design, etc. means that the actual range is usually much less (e.g., they amost have to touch). Also note that there are timing constraints so you may need to make the scheduling priority of the interrupt thread of your NFC driver real-time. Mark --