Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2870024pxb; Fri, 12 Feb 2021 03:39:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJxqkiLq0+/m3Xh3LEDpQQnyF5aqVLUziYR915BiH4DwuDxXT9McTpfW0r0KBXbJoCq61qgK X-Received: by 2002:a17:906:384c:: with SMTP id w12mr2611406ejc.140.1613129975715; Fri, 12 Feb 2021 03:39:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613129975; cv=none; d=google.com; s=arc-20160816; b=t+6e6fzP6pUHhL92miZfTm+cEh7b0d8eRtkksIAtJ04JU/xxlZcFHe+0ZRIbJU7CW8 mCIigxWOaTtvyWwrOw426hftbha1rytmz9quhm8PlQnTMVmtzNRaUxX8dfMgLY2KXUxt gbriESSOiSLp7qpaksPWAisRrQVTZbhBtPA4zxW0ckItLHexI7MdmB/OxSpEowIQqel9 dCiYOOhVaZ+ygR8KNkMFPndlE+mgTyGBtsj+6/cm/m65cIaVSZf5OkVLX1Q7FdYq0koF gVRtKZQFIF8+65JPC8g63xU5OziG3PkNata3sbL6gxBT4s0XHfwG45oVjjL/2qf33zt0 bIbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :to:subject:dkim-signature; bh=LB8dl2RxIN//zhj+ja02xt445NXNMzDjJQYs9Xwtfa8=; b=JDQ9/3fJAReukTeQ5Eud0QI/rifJ3LYSfiEsI8Maux4fscz9jdngB7MY3nTYSPXTKI 68ShQhwLQP/ECuYvEP8AE6pQRj3AVjLAwBRvirUUQOWznPagxDe+zCudITwOgml2RAE3 5otsWrLpnIBKoXlyePEfxWaTlXjSk2nYDvpAzqak8PoJzkLjhj8OJQOOOIr3j/3/HtKP X6UCGkmhxYr7EpNZcZE1wbTXAOY8KEtzrTa6620FiGMKMz6cy7dLBOLD4qdtVf8gYuvS 7TB4ch6M8nQQdBm3d6dTIpMrcsXsMMK5HtoyB+uEC3toFh95+acu9sc2vO8K2lUYU5ZZ eaXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@metafoo.de header.s=default2002 header.b=e9IXiEEb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=metafoo.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l3si6663780ejd.83.2021.02.12.03.39.12; Fri, 12 Feb 2021 03:39:35 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@metafoo.de header.s=default2002 header.b=e9IXiEEb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=metafoo.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230246AbhBLLgq (ORCPT + 99 others); Fri, 12 Feb 2021 06:36:46 -0500 Received: from www381.your-server.de ([78.46.137.84]:36544 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230242AbhBLLg3 (ORCPT ); Fri, 12 Feb 2021 06:36:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=metafoo.de; s=default2002; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID; bh=LB8dl2RxIN//zhj+ja02xt445NXNMzDjJQYs9Xwtfa8=; b=e9IXiEEbfCytoXcIB16bx+BsX2 fAjG5vY/bS6142DoNUvUHl6fHqL7qlLIEvw4KhCcB+/sqMWwMWwKf0Krj+ZQTFs0SYbAsAWCVZRdB BQXfSWgJNf24IE9TcHUQ+1JdxHRur/HTjq1IG0XFmG67ihEe0n37BnH/1X89tsXdwmH4M7C3R7lo1 R7m03oyPPYdgws6DhQpiz6g95v5qeuGWO+t/Qs0aMiLRpNv+xIMIYGTxmEO5zJuSiQaO5m+1bLiIn iM7VclnBdVzpdwQZo/RVasz/2KyyHF6EmM5lIu4oyetGSo3yYA1X5ouWp1rYhsf15OrnRIYvgcmro omrqMG1Q==; Received: from sslproxy02.your-server.de ([78.47.166.47]) by www381.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1lAWjY-00046S-9b; Fri, 12 Feb 2021 12:35:36 +0100 Received: from [62.216.202.92] (helo=[192.168.178.20]) by sslproxy02.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAWjY-000F1M-4X; Fri, 12 Feb 2021 12:35:36 +0100 Subject: Re: Adding custom functional callbacks to IIO driver To: Anand Ashok Dumbre , Jonathan Cameron , "knaack.h@gmx.de" , Peter Meerwald-Stadler , Michal Simek , "linux-iio@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" References: From: Lars-Peter Clausen Message-ID: Date: Fri, 12 Feb 2021 12:35:35 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Authenticated-Sender: lars@metafoo.de X-Virus-Scanned: Clear (ClamAV 0.102.4/26077/Thu Feb 11 13:18:43 2021) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/12/21 12:07 PM, Anand Ashok Dumbre wrote: > Hello, > > I have an IIO adc driver that measures temperatures and voltages on the SOC. > There are other kernel modules interested in the temperature and voltage event information. > > Would using a custom callback registration mechanism be advisable? > Is there something similar done already in IIO that can be leveraged? Hi, Have a look at the IIO consumer API that allows other kernel modules to subscribe to the output of an IIO device. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/iio/consumer.h - Lars