Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp126365ybt; Tue, 16 Jun 2020 18:43:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrckVOX9L+eZzGVufhv17dWcfWbNzjyzVS5cDuqp4OLjvTxWlff9qO06+ciA6xAmvJX1BS X-Received: by 2002:a17:906:3653:: with SMTP id r19mr5126602ejb.246.1592358210244; Tue, 16 Jun 2020 18:43:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592358210; cv=none; d=google.com; s=arc-20160816; b=fe+rm812PMvI4W/ObPKAQa5p7LF3LSi9zz/iX+T9NnyxwMzv7Lc8L8UHGYwR1k/cFe gi8jpS2Ne0sW/qbJ7V46A0AuxEaViAjXRcwWBNHwgkhxqXALQUyxFHNHNdWLywjHnj/i Ar2drnxkknqBO03MENAKMWIGBqiDwLRb0L7d2ekODY5qtlfHAiPqWG7WTGi+sjE2meCY 3XdbMBgOgejpsj60DlRuNzNDu0PQZHfvfhzLoqx/Fjkg7WY8hYmhHRbcbPkNR8Nqwo8o Bvm2zbt8e0reIlS1Y/RK/Bts0cbNevk53+URE5EoPg3hhCoCipd3soAg0hRIxZo7Oxuj ymjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=GXEE14mzFR5Jx4D5AnsgrO8APD2gqcIapef9MSMNq20=; b=RBQC9O4cnTNtftjPVkDDVcVY1AC4jsdMFWI0qJVCtJkssYdC+Aa0N2LZqNOnBE59Zo a86j8s9QF2DqtigphtnVGE8PH1jCcJqvSeWAYhdhCLhrD99pCcQiFCf5hrGDR5rACotF hif1l654pYbaW6e6egQyq3zUK7cMjz79VAHiqzQo4pJRc77ciUKIZpb5HvY6LN5Moqx3 hLkDzzj9WwtTbBJNiK0QtcZLatJGBVaLv2Iov+EwVbIgwJhxUsqMf8rHZGAordSmHbYK 8iqG6M49XlGISL/LL3feGW4Z0SRPDwsvqSKCv4BcW7aUztR4KBi9mDVh4fUzLxId1EcV WHJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=knrbZeAR; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id um1si12103757ejb.200.2020.06.16.18.43.08; Tue, 16 Jun 2020 18:43:30 -0700 (PDT) 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=@gmail.com header.s=20161025 header.b=knrbZeAR; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726955AbgFQBkq (ORCPT + 99 others); Tue, 16 Jun 2020 21:40:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726941AbgFQBkl (ORCPT ); Tue, 16 Jun 2020 21:40:41 -0400 Received: from mail-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B76A4C06174E; Tue, 16 Jun 2020 18:40:40 -0700 (PDT) Received: by mail-qt1-x841.google.com with SMTP id c12so335259qtq.11; Tue, 16 Jun 2020 18:40:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=GXEE14mzFR5Jx4D5AnsgrO8APD2gqcIapef9MSMNq20=; b=knrbZeAR9Z6oZnogbdjFIm6Fbq/ilMe+1FJklyM0Uj4GEy/Epxsz3tWBi3MMiol1PX jLe5RfXbKs1VRUNsuv7t6EXQVGMuOneU1zXIECoQTz3OaMYDMw0wNgNFAKnaBXYdveZb C5jIX0e1oygn48yVaxQUrFQFRaGu71/LBWBJE3N/MV70ibM3EZwBr2Fy10oGLeOpi2h7 G/hRq3ltthYPfuW6RDLgp7VoggJNeLCr4rzPY3+lDTCeeQoe83ygpE8+I6I1UjFxRj8B U84O6IPlBmzJrepR2BCnBWAaH+4+C0LoxiMAsuyY6h4Embb9bWPtRKPX/hEzKCYvBrsH mjQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=GXEE14mzFR5Jx4D5AnsgrO8APD2gqcIapef9MSMNq20=; b=BUfCNTOVAgTu/AppjFwx8w8N4IObsZLgBXfqY7P0gs0UN5ZhqOuT38KbzBUoC1g4Gx EOPhNMcM5RCx+tY2maWKsVFRqHjMbSv14pA26uEChM6MJwCrkiSUMSED7ISNSApIGA5M QrB8ocTEsoO+EDGkDfINEH6jAGXZ+qs7adaLRyORZPnu5NVPERsDcoqXtfVtA8EUF3/e bd6BDlAqWB3RiaKiL2m4UCeiI4yOD3whz3rmKlPOu+ACmG3yHaX+QLLnStHwwc0LopP5 63DKuEFvDA5tyGOnDOyCl3v/sX+ZbzMLMrsAQ4OFfLLKb31iY2dTdVj0e/eeSA5PXmtJ wdvw== X-Gm-Message-State: AOAM5326sn0AVb2rksIp6IVyWLxOgkOVg78Ver+JhXY+L12yFncB2zKy vPUQUyjguHbDvREk4txsk24= X-Received: by 2002:ac8:42ce:: with SMTP id g14mr24158254qtm.117.1592358039778; Tue, 16 Jun 2020 18:40:39 -0700 (PDT) Received: from localhost.localdomain (072-189-064-225.res.spectrum.com. [72.189.64.225]) by smtp.gmail.com with ESMTPSA id a14sm1917014qkn.16.2020.06.16.18.40.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jun 2020 18:40:39 -0700 (PDT) From: William Breathitt Gray To: jic23@kernel.org Cc: kamel.bouhara@bootlin.com, gwendal@chromium.org, alexandre.belloni@bootlin.com, david@lechnology.com, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, syednwaris@gmail.com, patrick.havelange@essensium.com, fabrice.gasnier@st.com, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com, William Breathitt Gray Subject: [PATCH v3 2/4] docs: counter: Update to reflect sysfs internalization Date: Tue, 16 Jun 2020 21:40:00 -0400 Message-Id: <836331743a80c6720a2f501582aa7649e236bbac.1592341702.git.vilhelm.gray@gmail.com> X-Mailer: git-send-email 2.26.2 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The Counter subsystem architecture and driver implementations have changed in order to handle Counter sysfs interactions in a more consistent way. This patch updates the Generic Counter interface documentation to reflect the changes. Signed-off-by: William Breathitt Gray --- Documentation/driver-api/generic-counter.rst | 216 +++++++++++++------ 1 file changed, 150 insertions(+), 66 deletions(-) diff --git a/Documentation/driver-api/generic-counter.rst b/Documentation/driver-api/generic-counter.rst index e622f8f6e56a..8aaa6cd37fd4 100644 --- a/Documentation/driver-api/generic-counter.rst +++ b/Documentation/driver-api/generic-counter.rst @@ -250,8 +250,8 @@ for defining a counter device. .. kernel-doc:: drivers/counter/counter.c :export: -Implementation -============== +Driver Implementation +===================== To support a counter device, a driver must first allocate the available Counter Signals via counter_signal structures. These Signals should @@ -267,25 +267,59 @@ respective counter_count structure. These counter_count structures are set to the counts array member of an allocated counter_device structure before the Counter is registered to the system. -Driver callbacks should be provided to the counter_device structure via -a constant counter_ops structure in order to communicate with the -device: to read and write various Signals and Counts, and to set and get -the "action mode" and "function mode" for various Synapses and Counts -respectively. +Driver callbacks must be provided to the counter_device structure in +order to communicate with the device: to read and write various Signals +and Counts, and to set and get the "action mode" and "function mode" for +various Synapses and Counts respectively. A defined counter_device structure may be registered to the system by passing it to the counter_register function, and unregistered by passing it to the counter_unregister function. Similarly, the -devm_counter_register and devm_counter_unregister functions may be used -if device memory-managed registration is desired. - -Extension sysfs attributes can be created for auxiliary functionality -and data by passing in defined counter_device_ext, counter_count_ext, -and counter_signal_ext structures. In these cases, the -counter_device_ext structure is used for global/miscellaneous exposure -and configuration of the respective Counter device, while the -counter_count_ext and counter_signal_ext structures allow for auxiliary -exposure and configuration of a specific Count or Signal respectively. +devm_counter_register function may be used if device memory-managed +registration is desired. + +The struct counter_data structure is used to define counter extensions +for Signals, Synapses, and Counts. + +The "type" member specifies the type of high-level data (e.g. BOOL, +COUNT_DIRECTION, etc.) handled by this extension. The "`*_read`" and +"`*_write`" members can then be set by the counter device driver with +callbacks to handle that data using native C data types (i.e. u8, u64, +etc.). + +Convenience macros such as `COUNTER_DATA_COUNT_U64` are provided for use +by driver authors. In particular, driver authors are expected to use +the provided macros for standard Counter subsystem attributes in order +to maintain a consistent interface for userspace. For example, a counter +device driver may define several standard attributes like so:: + + struct counter_data count_ext[] = { + COUNTER_DATA_DIRECTION(count_direction_read), + COUNTER_DATA_ENABLE(count_enable_read, count_enable_write), + COUNTER_DATA_CEILING(count_ceiling_read, count_ceiling_write), + }; + +This makes it simple to see, add, and modify the attributes that are +supported by this driver ("direction", "enable", and "ceiling") and to +maintain this code without getting lost in a web of struct braces. + +Callbacks must match the function type expected for the respective +component or extension. These function types are defined in the struct +counter_data structure as the "`*_read`" and "`*_write`" union members. + +The corresponding callback prototypes for the extensions mentioned in +the previous example above would be:: + + int count_direction_read(struct counter_device *counter, + struct counter_count *count, u8 *direction); + int count_enable_read(struct counter_device *counter, + struct counter_count *count, u8 *enable); + int count_enable_write(struct counter_device *counter, + struct counter_count *count, u8 enable); + int count_ceiling_read(struct counter_device *counter, + struct counter_count *count, u64 *ceiling); + int count_ceiling_write(struct counter_device *counter, + struct counter_count *count, u64 ceiling); Determining the type of extension to create is a matter of scope. @@ -313,52 +347,102 @@ Determining the type of extension to create is a matter of scope. chip overheated via a device extension called "error_overtemp": /sys/bus/counter/devices/counterX/error_overtemp -Architecture -============ - -When the Generic Counter interface counter module is loaded, the -counter_init function is called which registers a bus_type named -"counter" to the system. Subsequently, when the module is unloaded, the -counter_exit function is called which unregisters the bus_type named -"counter" from the system. - -Counter devices are registered to the system via the counter_register -function, and later removed via the counter_unregister function. The -counter_register function establishes a unique ID for the Counter -device and creates a respective sysfs directory, where X is the -mentioned unique ID: - - /sys/bus/counter/devices/counterX - -Sysfs attributes are created within the counterX directory to expose -functionality, configurations, and data relating to the Counts, Signals, -and Synapses of the Counter device, as well as options and information -for the Counter device itself. - -Each Signal has a directory created to house its relevant sysfs -attributes, where Y is the unique ID of the respective Signal: - - /sys/bus/counter/devices/counterX/signalY - -Similarly, each Count has a directory created to house its relevant -sysfs attributes, where Y is the unique ID of the respective Count: - - /sys/bus/counter/devices/counterX/countY - -For a more detailed breakdown of the available Generic Counter interface -sysfs attributes, please refer to the -Documentation/ABI/testing/sysfs-bus-counter file. - -The Signals and Counts associated with the Counter device are registered -to the system as well by the counter_register function. The -signal_read/signal_write driver callbacks are associated with their -respective Signal attributes, while the count_read/count_write and -function_get/function_set driver callbacks are associated with their -respective Count attributes; similarly, the same is true for the -action_get/action_set driver callbacks and their respective Synapse -attributes. If a driver callback is left undefined, then the respective -read/write permission is left disabled for the relevant attributes. - -Similarly, extension sysfs attributes are created for the defined -counter_device_ext, counter_count_ext, and counter_signal_ext -structures that are passed in. +Subsystem Architecture +====================== + +Counter drivers pass and take data natively (i.e. `u8`, `u64`, etc.) and +the shared counter module handles the translation between the sysfs +interface. This gurantees a standard userspace interface for all counter +drivers, and helps generalize the Generic Counter driver ABI in order to +support the Generic Counter chrdev interface without significant changes +to the existing counter drivers. + +A high-level view of how a count value is passed down from a counter +driver is exemplified by the following:: + + Count data request: + ~~~~~~~~~~~~~~~~~~~ + ---------------------- + / Counter device \ + +----------------------+ + | Count register: 0x28 | + +----------------------+ + | + ----------------- + / raw count data / + ----------------- + | + V + +----------------------------+ + | Counter device driver |----------+ + +----------------------------+ | + | Processes data from device | ------------------- + |----------------------------| / driver callbacks / + | Type: unsigned long | ------------------- + | Value: 42 | | + +----------------------------+ | + | | + ---------------- | + / unsigned long / | + ---------------- | + | | + | V + | +----------------------+ + | | Counter core | + | +----------------------+ + | | Routes device driver | + | | callbacks to the | + | | userspace interfaces | + | +----------------------+ + | | + | ------------------- + | / driver callbacks / + | ------------------- + | | + +-------+ | + | | + | +---------------+ + | | + V | + +--------------------+ | + | Counter sysfs |<-+ + +--------------------+ + | Translates to the | + | standard Counter | + | sysfs output | + |--------------------| + | Type: const char * | + | Value: "42" | + +--------------------+ + | + --------------- + / const char * / + --------------- + | + V + +--------------------------------------------------+ + | `/sys/bus/counter/devices/counterX/countY/count` | + +--------------------------------------------------+ + \ Count: "42" / + -------------------------------------------------- + +There are three primary components involved: + +Counter device driver +--------------------- +Communicates with the hardware device to read/write data; e.g. counter +drivers for quadrature encoders, timers, etc. + +Counter core +------------ +Registers the counter device driver to the system so that the respective +callbacks are called during userspace interaction. + +Counter sysfs +------------- +Translates counter data to the standard Counter sysfs interface format +and vice versa. + +Please refer to the `Documentation/ABI/testing/sysfs-bus-counter` file +for a detailed breakdown of the available Generic Counter interface +sysfs attributes. -- 2.26.2