Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3962798ybg; Fri, 25 Oct 2019 11:20:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqyTuCBWx614yQyGYjnbY1sU5jcxN2b6AyjH6oq+bf6UEaot+erSJbHF03F/iUmVX2UJwvQa X-Received: by 2002:a17:907:10d3:: with SMTP id rv19mr4567529ejb.301.1572027640987; Fri, 25 Oct 2019 11:20:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572027640; cv=none; d=google.com; s=arc-20160816; b=ZXmV/8uMwuft79kv0fPnM1rgWCfUb29X/5OF71owxTYgBQMeKmxzFA7eA+LYJ/FBqh 9bax5Y2EfuDidcPr/KLO9wOUUCvBT+YSS1DDZZSwV6RXmXh1g8uLs5ENzrnf1JJX/NL2 xaa/vVAZqE0mFWosFb+/GPoSiLfpsMtkNajl1j8IncNF8Bgvl57QRmGf/iyIQCjXUmaL fhgH20LwqrcFfk0nc2Qn4yPh9UhBtwURe5vZYLNyEO33iSn2KQO1ZqSB6XlnfgPpesKj pBeEEHKFl9JY2ZWwkujdA++woQnC7k8S46BRkfG5uXaraeltFZJtvalWf2mzQu5abrWN mSOw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Qb6AfZWTJWrvmhoO9k7cdyf5vht6+XH6bsZsRm94V08=; b=EMRihOv7dEpd3UEtZx/MmgzEB9jlzttw7aMlF/uW9aQ1navQfHtfgpkfqavTRF+o1G EAR+t0JKydpizavQtigLop4Dr9ppeNtGHZ5Na6huhroDpyPyVJhlADFMEW62nbhjxVEJ ENModVL2TplNyU4RocrdDGNknUuEAMBwI9oTmHErk7NG6Inqvy7J/JJtnQeumb4iwFYN 1E4INaPNiMRiYaRZOSormlke4kiATZSCmRK6j2RCVJsGt6k+umFPpAlV3dUv+knYTFHw 70AmZgV/vAQOc/KKx/RhIEDBP+uHtGLmCRP/nCqW4e6Tg/u71nrZLmo2Mks27Axe7A2V J67A== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j17si1605519ejd.314.2019.10.25.11.20.17; Fri, 25 Oct 2019 11:20:40 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2410039AbfJXRDS (ORCPT + 99 others); Thu, 24 Oct 2019 13:03:18 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:54862 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730622AbfJXRDR (ORCPT ); Thu, 24 Oct 2019 13:03:17 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: eballetbo) with ESMTPSA id 79FD8286063 Subject: Re: [PATCH v2 01/18] platform: chrome: Put docs with the code To: Jonathan Cameron , Gwendal Grignou Cc: briannorris@chromium.org, knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net, lee.jones@linaro.org, bleung@chromium.org, dianders@chromium.org, groeck@chromium.org, fabien.lahoudere@collabora.com, linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org References: <20191021055403.67849-1-gwendal@chromium.org> <20191021055403.67849-2-gwendal@chromium.org> <20191021163134.6d121b1e@archlinux> From: Enric Balletbo i Serra Message-ID: <50b45b37-d02e-df9a-1ce5-54cea23debb6@collabora.com> Date: Thu, 24 Oct 2019 19:03:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191021163134.6d121b1e@archlinux> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21/10/19 17:31, Jonathan Cameron wrote: > On Sun, 20 Oct 2019 22:53:46 -0700 > Gwendal Grignou wrote: > >> To avoid doc rot, put function documentations with code, not header. >> Use kernel-doc style comments for exported functions. >> >> Signed-off-by: Gwendal Grignou > Looks good to me. > > Acked-by: Jonathan Cameron > applied for 5.5, thanks. >> --- >> New in v2. >> >> drivers/platform/chrome/cros_ec.c | 33 +++++++ >> drivers/platform/chrome/cros_ec_proto.c | 70 +++++++++++++ >> include/linux/platform_data/cros_ec_proto.h | 103 -------------------- >> 3 files changed, 103 insertions(+), 103 deletions(-) >> >> diff --git a/drivers/platform/chrome/cros_ec.c b/drivers/platform/chrome/cros_ec.c >> index fd77e6fa74c2c..9b2d07422e175 100644 >> --- a/drivers/platform/chrome/cros_ec.c >> +++ b/drivers/platform/chrome/cros_ec.c >> @@ -104,6 +104,15 @@ static int cros_ec_sleep_event(struct cros_ec_device *ec_dev, u8 sleep_event) >> return ret; >> } >> >> +/** >> + * cros_ec_register() - Register a new ChromeOS EC, using the provided info. >> + * @ec_dev: Device to register. >> + * >> + * Before calling this, allocate a pointer to a new device and then fill >> + * in all the fields up to the --private-- marker. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_register(struct cros_ec_device *ec_dev) >> { >> struct device *dev = ec_dev->dev; >> @@ -198,6 +207,14 @@ int cros_ec_register(struct cros_ec_device *ec_dev) >> } >> EXPORT_SYMBOL(cros_ec_register); >> >> +/** >> + * cros_ec_unregister() - Remove a ChromeOS EC. >> + * @ec_dev: Device to unregister. >> + * >> + * Call this to deregister a ChromeOS EC, then clean up any private data. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_unregister(struct cros_ec_device *ec_dev) >> { >> if (ec_dev->pd) >> @@ -209,6 +226,14 @@ int cros_ec_unregister(struct cros_ec_device *ec_dev) >> EXPORT_SYMBOL(cros_ec_unregister); >> >> #ifdef CONFIG_PM_SLEEP >> +/** >> + * cros_ec_suspend() - Handle a suspend operation for the ChromeOS EC device. >> + * @ec_dev: Device to suspend. >> + * >> + * This can be called by drivers to handle a suspend event. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_suspend(struct cros_ec_device *ec_dev) >> { >> struct device *dev = ec_dev->dev; >> @@ -243,6 +268,14 @@ static void cros_ec_report_events_during_suspend(struct cros_ec_device *ec_dev) >> 1, ec_dev); >> } >> >> +/** >> + * cros_ec_resume() - Handle a resume operation for the ChromeOS EC device. >> + * @ec_dev: Device to resume. >> + * >> + * This can be called by drivers to handle a resume event. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_resume(struct cros_ec_device *ec_dev) >> { >> int ret; >> diff --git a/drivers/platform/chrome/cros_ec_proto.c b/drivers/platform/chrome/cros_ec_proto.c >> index f659f96bda128..7db58771ec77c 100644 >> --- a/drivers/platform/chrome/cros_ec_proto.c >> +++ b/drivers/platform/chrome/cros_ec_proto.c >> @@ -117,6 +117,17 @@ static int send_command(struct cros_ec_device *ec_dev, >> return ret; >> } >> >> +/** >> + * cros_ec_prepare_tx() - Prepare an outgoing message in the output buffer. >> + * @ec_dev: Device to register. >> + * @msg: Message to write. >> + * >> + * This is intended to be used by all ChromeOS EC drivers, but at present >> + * only SPI uses it. Once LPC uses the same protocol it can start using it. >> + * I2C could use it now, with a refactor of the existing code. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_prepare_tx(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg) >> { >> @@ -141,6 +152,16 @@ int cros_ec_prepare_tx(struct cros_ec_device *ec_dev, >> } >> EXPORT_SYMBOL(cros_ec_prepare_tx); >> >> +/** >> + * cros_ec_check_result() - Check ec_msg->result. >> + * @ec_dev: EC device. >> + * @msg: Message to check. >> + * >> + * This is used by ChromeOS EC drivers to check the ec_msg->result for >> + * errors and to warn about them. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_check_result(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg) >> { >> @@ -326,6 +347,13 @@ static int cros_ec_get_host_command_version_mask(struct cros_ec_device *ec_dev, >> return ret; >> } >> >> +/** >> + * cros_ec_query_all() - Query the protocol version supported by the >> + * ChromeOS EC. >> + * @ec_dev: Device to register. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_query_all(struct cros_ec_device *ec_dev) >> { >> struct device *dev = ec_dev->dev; >> @@ -453,6 +481,16 @@ int cros_ec_query_all(struct cros_ec_device *ec_dev) >> } >> EXPORT_SYMBOL(cros_ec_query_all); >> >> +/** >> + * cros_ec_cmd_xfer() - Send a command to the ChromeOS EC. >> + * @ec_dev: EC device. >> + * @msg: Message to write. >> + * >> + * Call this to send a command to the ChromeOS EC. This should be used >> + * instead of calling the EC's cmd_xfer() callback directly. >> + * >> + * Return: 0 on success or negative error code. >> + */ >> int cros_ec_cmd_xfer(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg) >> { >> @@ -500,6 +538,18 @@ int cros_ec_cmd_xfer(struct cros_ec_device *ec_dev, >> } >> EXPORT_SYMBOL(cros_ec_cmd_xfer); >> >> +/** >> + * cros_ec_cmd_xfer_status() - Send a command to the ChromeOS EC. >> + * @ec_dev: EC device. >> + * @msg: Message to write. >> + * >> + * This function is identical to cros_ec_cmd_xfer, except it returns success >> + * status only if both the command was transmitted successfully and the EC >> + * replied with success status. It's not necessary to check msg->result when >> + * using this function. >> + * >> + * Return: The number of bytes transferred on success or negative error code. >> + */ >> int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg) >> { >> @@ -584,6 +634,16 @@ static int get_keyboard_state_event(struct cros_ec_device *ec_dev) >> return ec_dev->event_size; >> } >> >> +/** >> + * cros_ec_get_next_event() - Fetch next event from the ChromeOS EC. >> + * @ec_dev: Device to fetch event from. >> + * @wake_event: Pointer to a bool set to true upon return if the event might be >> + * treated as a wake event. Ignored if null. >> + * >> + * Return: negative error code on errors; 0 for no data; or else number of >> + * bytes received (i.e., an event was retrieved successfully). Event types are >> + * written out to @ec_dev->event_data.event_type on success. >> + */ >> int cros_ec_get_next_event(struct cros_ec_device *ec_dev, bool *wake_event) >> { >> u8 event_type; >> @@ -628,6 +688,16 @@ int cros_ec_get_next_event(struct cros_ec_device *ec_dev, bool *wake_event) >> } >> EXPORT_SYMBOL(cros_ec_get_next_event); >> >> +/** >> + * cros_ec_get_host_event() - Return a mask of event set by the ChromeOS EC. >> + * @ec_dev: Device to fetch event from. >> + * >> + * When MKBP is supported, when the EC raises an interrupt, we collect the >> + * events raised and call the functions in the ec notifier. This function >> + * is a helper to know which events are raised. >> + * >> + * Return: 0 on error or non-zero bitmask of one or more EC_HOST_EVENT_*. >> + */ >> u32 cros_ec_get_host_event(struct cros_ec_device *ec_dev) >> { >> u32 host_event; >> diff --git a/include/linux/platform_data/cros_ec_proto.h b/include/linux/platform_data/cros_ec_proto.h >> index eab7036cda090..0d4e4aaed37af 100644 >> --- a/include/linux/platform_data/cros_ec_proto.h >> +++ b/include/linux/platform_data/cros_ec_proto.h >> @@ -187,133 +187,30 @@ struct cros_ec_platform { >> u16 cmd_offset; >> }; >> >> -/** >> - * cros_ec_suspend() - Handle a suspend operation for the ChromeOS EC device. >> - * @ec_dev: Device to suspend. >> - * >> - * This can be called by drivers to handle a suspend event. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_suspend(struct cros_ec_device *ec_dev); >> >> -/** >> - * cros_ec_resume() - Handle a resume operation for the ChromeOS EC device. >> - * @ec_dev: Device to resume. >> - * >> - * This can be called by drivers to handle a resume event. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_resume(struct cros_ec_device *ec_dev); >> >> -/** >> - * cros_ec_prepare_tx() - Prepare an outgoing message in the output buffer. >> - * @ec_dev: Device to register. >> - * @msg: Message to write. >> - * >> - * This is intended to be used by all ChromeOS EC drivers, but at present >> - * only SPI uses it. Once LPC uses the same protocol it can start using it. >> - * I2C could use it now, with a refactor of the existing code. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_prepare_tx(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg); >> >> -/** >> - * cros_ec_check_result() - Check ec_msg->result. >> - * @ec_dev: EC device. >> - * @msg: Message to check. >> - * >> - * This is used by ChromeOS EC drivers to check the ec_msg->result for >> - * errors and to warn about them. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_check_result(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg); >> >> -/** >> - * cros_ec_cmd_xfer() - Send a command to the ChromeOS EC. >> - * @ec_dev: EC device. >> - * @msg: Message to write. >> - * >> - * Call this to send a command to the ChromeOS EC. This should be used >> - * instead of calling the EC's cmd_xfer() callback directly. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_cmd_xfer(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg); >> >> -/** >> - * cros_ec_cmd_xfer_status() - Send a command to the ChromeOS EC. >> - * @ec_dev: EC device. >> - * @msg: Message to write. >> - * >> - * This function is identical to cros_ec_cmd_xfer, except it returns success >> - * status only if both the command was transmitted successfully and the EC >> - * replied with success status. It's not necessary to check msg->result when >> - * using this function. >> - * >> - * Return: The number of bytes transferred on success or negative error code. >> - */ >> int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev, >> struct cros_ec_command *msg); >> >> -/** >> - * cros_ec_register() - Register a new ChromeOS EC, using the provided info. >> - * @ec_dev: Device to register. >> - * >> - * Before calling this, allocate a pointer to a new device and then fill >> - * in all the fields up to the --private-- marker. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_register(struct cros_ec_device *ec_dev); >> >> -/** >> - * cros_ec_unregister() - Remove a ChromeOS EC. >> - * @ec_dev: Device to unregister. >> - * >> - * Call this to deregister a ChromeOS EC, then clean up any private data. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_unregister(struct cros_ec_device *ec_dev); >> >> -/** >> - * cros_ec_query_all() - Query the protocol version supported by the >> - * ChromeOS EC. >> - * @ec_dev: Device to register. >> - * >> - * Return: 0 on success or negative error code. >> - */ >> int cros_ec_query_all(struct cros_ec_device *ec_dev); >> >> -/** >> - * cros_ec_get_next_event() - Fetch next event from the ChromeOS EC. >> - * @ec_dev: Device to fetch event from. >> - * @wake_event: Pointer to a bool set to true upon return if the event might be >> - * treated as a wake event. Ignored if null. >> - * >> - * Return: negative error code on errors; 0 for no data; or else number of >> - * bytes received (i.e., an event was retrieved successfully). Event types are >> - * written out to @ec_dev->event_data.event_type on success. >> - */ >> int cros_ec_get_next_event(struct cros_ec_device *ec_dev, bool *wake_event); >> >> -/** >> - * cros_ec_get_host_event() - Return a mask of event set by the ChromeOS EC. >> - * @ec_dev: Device to fetch event from. >> - * >> - * When MKBP is supported, when the EC raises an interrupt, we collect the >> - * events raised and call the functions in the ec notifier. This function >> - * is a helper to know which events are raised. >> - * >> - * Return: 0 on error or non-zero bitmask of one or more EC_HOST_EVENT_*. >> - */ >> u32 cros_ec_get_host_event(struct cros_ec_device *ec_dev); >> >> #endif /* __LINUX_CROS_EC_PROTO_H */ >