Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp740632ybl; Thu, 23 Jan 2020 06:59:16 -0800 (PST) X-Google-Smtp-Source: APXvYqyaFDN5T+fNtNpNOlH+yuQryFok8q3YXA9QvhBojodDEbqAuwMPZt9QGmq1MF0O1ZougpXx X-Received: by 2002:a54:4595:: with SMTP id z21mr10896700oib.136.1579791555992; Thu, 23 Jan 2020 06:59:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579791555; cv=none; d=google.com; s=arc-20160816; b=V/3y7HxA5pO3KvL7w4JHUDUefnznkiNgCcGt7HER8i46JJ0SU8GF5Bfz9o7hGr0/Sg i61GLA2LnyT//3FzEt5xa/Pu19PO1xoZ34Ex+Dl2YAA7MsZs4KFrylQddp/z9J8xm+Ko 6xmVCNqjrE7Mj5NRerj3FMiv2SekqdBY9uR8Jqsm6f9v0Md9kmD5HU6Iyx7RRuWbwlKd ugfHvKimG6Kc/9i5lWBOMHzemA6y1n7NBXdFOG47AdYWhOQpI41ncoXs2fJXGp5BIdVZ BBcelp9b4ZtGSA//8GcFnRKtm7+8MLi+95AV4Pcl5NHfxr19bRa0A8wiT8SLBJjHjxAR KL5Q== 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; bh=WrxcEdUyORlO9vrw8RWspm4oJkNrTnFmL5g6BVwQ89k=; b=FiJvoLFa8db9GsLcKsoM10TTfcaHngMbaeIJ1fdGEu9D8eszzt3Jgv2aNlA9nV7/Rt bxgLNJSLEF8bEL1oz0JA+7W1f92QP888IWjjcZA5nkEJ9z7Lm2FgdWTlQUf3aFdBighn q8n6Afg0ANI0tUjv4eAJdb7isH5ropdHceOu0wIupssAq8RkVVbFFgAjJWFHB9jLQJi5 xMqcAOdXG4h8NTURSnuROB4SUx+2P/yG+ZsHMqh8mfrE65i2CREAT9+Ou2wJwFHRUaP4 bMB6fJWEF1EQzSLIfz2dSonbEtPUKtcGiVqnHAgBEi5i+cvo+c5pgc6hSr4ynfsJQttU KpCg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f4si874764oij.133.2020.01.23.06.59.03; Thu, 23 Jan 2020 06:59:15 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728901AbgAWO6F (ORCPT + 99 others); Thu, 23 Jan 2020 09:58:05 -0500 Received: from hostingweb31-40.netsons.net ([89.40.174.40]:57658 "EHLO hostingweb31-40.netsons.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726811AbgAWO6F (ORCPT ); Thu, 23 Jan 2020 09:58:05 -0500 Received: from [109.168.11.45] (port=47594 helo=pc-ceresoli.dev.aim) by hostingweb31.netsons.net with esmtpa (Exim 4.92) (envelope-from ) id 1iudvl-0005F5-54; Thu, 23 Jan 2020 15:58:01 +0100 From: Luca Ceresoli To: linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org Cc: Luca Ceresoli , Wolfram Sang , Jean Delvare , Peter Rosin , linux-kernel@vger.kernel.org Subject: [PATCH v2 15/28] docs: i2c: smbus-protocol: enable kernel-doc function syntax Date: Thu, 23 Jan 2020 15:56:13 +0100 Message-Id: <20200123145626.8102-2-luca@lucaceresoli.net> X-Mailer: git-send-email 2.25.0 In-Reply-To: <20200123145626.8102-1-luca@lucaceresoli.net> References: <20200123135103.20540-1-luca@lucaceresoli.net> <20200123145626.8102-1-luca@lucaceresoli.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hostingweb31.netsons.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - lucaceresoli.net X-Get-Message-Sender-Via: hostingweb31.netsons.net: authenticated_id: luca+lucaceresoli.net/only user confirmed/virtual account not confirmed X-Authenticated-Sender: hostingweb31.netsons.net: luca@lucaceresoli.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hyperlinks from function names are not generated in headings. Move them in the plain text so they are rendered as clickable hyperlinks. While there also remove an unneeded colon in a heading. Signed-off-by: Luca Ceresoli Reviewed-by: Jean Delvare --- Changes in v2: - fix typo in commit message (Jean Delvare) --- Documentation/i2c/smbus-protocol.rst | 64 ++++++++++++++++++---------- 1 file changed, 42 insertions(+), 22 deletions(-) diff --git a/Documentation/i2c/smbus-protocol.rst b/Documentation/i2c/smbus-protocol.rst index 10c4a989982c..997945e90419 100644 --- a/Documentation/i2c/smbus-protocol.rst +++ b/Documentation/i2c/smbus-protocol.rst @@ -62,8 +62,10 @@ This sends a single bit to the device, at the place of the Rd/Wr bit:: Functionality flag: I2C_FUNC_SMBUS_QUICK -SMBus Receive Byte: i2c_smbus_read_byte() -========================================== +SMBus Receive Byte +================== + +Implemented by i2c_smbus_read_byte() This reads a single byte from a device, without specifying a device register. Some devices are so simple that this interface is enough; for @@ -75,8 +77,10 @@ the previous SMBus command:: Functionality flag: I2C_FUNC_SMBUS_READ_BYTE -SMBus Send Byte: i2c_smbus_write_byte() -======================================== +SMBus Send Byte +=============== + +Implemented by i2c_smbus_write_byte() This operation is the reverse of Receive Byte: it sends a single byte to a device. See Receive Byte for more information. @@ -88,8 +92,10 @@ to a device. See Receive Byte for more information. Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE -SMBus Read Byte: i2c_smbus_read_byte_data() -============================================ +SMBus Read Byte +=============== + +Implemented by i2c_smbus_read_byte_data() This reads a single byte from a device, from a designated register. The register is specified through the Comm byte:: @@ -99,8 +105,10 @@ The register is specified through the Comm byte:: Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA -SMBus Read Word: i2c_smbus_read_word_data() -============================================ +SMBus Read Word +=============== + +Implemented by i2c_smbus_read_word_data() This operation is very like Read Byte; again, data is read from a device, from a designated register that is specified through the Comm @@ -115,8 +123,10 @@ available for reads where the two data bytes are the other way around (not SMBus compliant, but very popular.) -SMBus Write Byte: i2c_smbus_write_byte_data() -============================================== +SMBus Write Byte +================ + +Implemented by i2c_smbus_write_byte_data() This writes a single byte to a device, to a designated register. The register is specified through the Comm byte. This is the opposite of @@ -129,8 +139,10 @@ the Read Byte operation. Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA -SMBus Write Word: i2c_smbus_write_word_data() -============================================== +SMBus Write Word +================ + +Implemented by i2c_smbus_write_word_data() This is the opposite of the Read Word operation. 16 bits of data is written to a device, to the designated register that is @@ -145,8 +157,8 @@ available for writes where the two data bytes are the other way around (not SMBus compliant, but very popular.) -SMBus Process Call: -=================== +SMBus Process Call +================== This command selects a device register (through the Comm byte), sends 16 bits of data to it, and reads 16 bits of data in return:: @@ -157,8 +169,10 @@ This command selects a device register (through the Comm byte), sends Functionality flag: I2C_FUNC_SMBUS_PROC_CALL -SMBus Block Read: i2c_smbus_read_block_data() -============================================== +SMBus Block Read +================ + +Implemented by i2c_smbus_read_block_data() This command reads a block of up to 32 bytes from a device, from a designated register that is specified through the Comm byte. The amount @@ -172,8 +186,10 @@ of data is specified by the device in the Count byte. Functionality flag: I2C_FUNC_SMBUS_READ_BLOCK_DATA -SMBus Block Write: i2c_smbus_write_block_data() -================================================ +SMBus Block Write +================= + +Implemented by i2c_smbus_write_block_data() The opposite of the Block Read command, this writes up to 32 bytes to a device, to a designated register that is specified through the @@ -274,8 +290,10 @@ I2C block transactions do not limit the number of bytes transferred but the SMBus layer places a limit of 32 bytes. -I2C Block Read: i2c_smbus_read_i2c_block_data() -================================================ +I2C Block Read +============== + +Implemented by i2c_smbus_read_i2c_block_data() This command reads a block of bytes from a device, from a designated register that is specified through the Comm byte:: @@ -286,8 +304,10 @@ designated register that is specified through the Comm byte:: Functionality flag: I2C_FUNC_SMBUS_READ_I2C_BLOCK -I2C Block Write: i2c_smbus_write_i2c_block_data() -================================================== +I2C Block Write +=============== + +Implemented by i2c_smbus_write_i2c_block_data() The opposite of the Block Read command, this writes bytes to a device, to a designated register that is specified through the -- 2.25.0