Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp700536imm; Wed, 18 Jul 2018 09:10:57 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeANO+ooTi/02gOXbDXFVjtg+wGsFgo8I/DezBPL9v7owY/ruZ9Yua7l7Qx9CyMl1GuSorl X-Received: by 2002:a65:4b87:: with SMTP id t7-v6mr6291935pgq.391.1531930257708; Wed, 18 Jul 2018 09:10:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531930257; cv=none; d=google.com; s=arc-20160816; b=cVWso4s+87PW6t6ODeq/c3a4yJVE5dyPlq30CyviZIO33IhhlOQYfFJBsKKqqAQvbr KSC7APcGJtGRpoac7d5XPMY74+EJWjNTYR/O9jnvkeLsScOYFTRORz8CQmWhuf3KYE5N zu7VtNrFv8vs2TOkt7HdcmpanBOq2mbVQYfOww0enkJ0ExBZs8io5nqULF9ib6OoDAGZ IxmTca1zjPr9CzTwUN9723AbdEnKknbOtvDCU9AhA212kep1Dz3L/CVBS0WjPSr/ntKI Bw/rLXdWc9fiEbVsLEpboZ/XCoZCNwkBXmLyI2R7QKcTKZixXn06Gvqo02qa0OtZcpLg Ub8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=KBWT4D49SNEbRp7ZPSD0l6ICdM3/bvJaNdYjgFwboE8=; b=VECW/QfBWkX0wfmCbOgsR0+zkRKMZ+GcPl2WKSAtmqxPX+dBq0aKK5LGOxBup34fQA Dgsf3JXZikaq8hrboRzU4pwLbuq6KWdZW6zF4mfI860/AdfezKI9v+IkLJX6R2/Nw6d7 12ui2JAYILKz4OqHWgbSambdqW+8Dw03/X7OXUKetP5UT7VhDBPua63bdM6jeq7Oz9Fd v7SOLIzP3mpWTbJXcH0GcQTBhIU/iA3bvOPEt1tT77PWbP6535WpPyAtJFfV/p83c/Dn +sOj3F3AW9D+ZG60rgO0m2hVUiKZ5HQStsBbFPJUlXw0ug+oEt1uoA4g9zVIJz6ILfcu +3fw== 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 z2-v6si3576692pfb.365.2018.07.18.09.10.41; Wed, 18 Jul 2018 09:10:57 -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 S1730998AbeGRQsk (ORCPT + 99 others); Wed, 18 Jul 2018 12:48:40 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:32774 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730110AbeGRQsk (ORCPT ); Wed, 18 Jul 2018 12:48:40 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: eballetbo) with ESMTPSA id 5966F279675 From: Enric Balletbo i Serra To: linux-kernel@vger.kernel.org Cc: groeck@chromium.org, bleung@chromium.org, kernel@collabora.com, lee.jones@linaro.org, Olof Johansson Subject: [PATCH 0/2] mfd: platform/chrome: some more cleanups between these subsystems. Date: Wed, 18 Jul 2018 18:09:54 +0200 Message-Id: <20180718160956.19864-1-enric.balletbo@collabora.com> X-Mailer: git-send-email 2.18.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Lee, Benson, This is another patchset to try to cleanup a bit more the interaction between the mfd subsystem and platform/chrome. The first patch moves some cros-ec include files from include/linux/mfd to platform/chrome. They are specific to the lpc transport driver and are not related to the mfd subsystem, so, there is no reason to have them living in include/linux/mfd. The second patch tries to cleanup and fix some kerneldoc commments in the remaining mfd/cros-ec include files. For now I only improved a bit the documentation and fixed the warnings reported by kerneldoc. I think that there is still a lot of improvement pending, specially in the cros_ec_commands.h file, but this is something I'd like to have the agreement of the chromeos folks as I know this file is used as interface for the EC firmware. As far as I know the kernel doesn't cares about this, but I know this is source of conflicts for the chromeos folks. Usually, in the chromeos kernel, the cros_ec_commands file is synced with the version available from the EC firmware but maybe we should reconsider this and have a well documented file in the kernel and sync in the other way. I am just thinking out loud. Best regards, Enric Enric Balletbo i Serra (2): platform/chrome: Move mfd/cros_ec_lpc* includes to drivers/platform. mfd: cros_ec: Fix and improve kerneldoc comments. drivers/mfd/cros_ec_dev.h | 13 +- drivers/platform/chrome/cros_ec_lpc.c | 3 +- drivers/platform/chrome/cros_ec_lpc_mec.c | 3 +- .../platform/chrome}/cros_ec_lpc_mec.h | 6 +- drivers/platform/chrome/cros_ec_lpc_reg.c | 3 +- .../platform/chrome}/cros_ec_lpc_reg.h | 6 +- include/linux/mfd/cros_ec.h | 214 +++++++------ include/linux/mfd/cros_ec_commands.h | 295 +++++++++++------- 8 files changed, 322 insertions(+), 221 deletions(-) rename {include/linux/mfd => drivers/platform/chrome}/cros_ec_lpc_mec.h (96%) rename {include/linux/mfd => drivers/platform/chrome}/cros_ec_lpc_reg.h (94%) -- 2.18.0