Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753327AbaKXMgD (ORCPT ); Mon, 24 Nov 2014 07:36:03 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:60004 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753230AbaKXMgA (ORCPT ); Mon, 24 Nov 2014 07:36:00 -0500 From: Arnd Bergmann To: Karol Wrona Cc: Jonathan Cameron , Samuel Ortiz , Lee Jones , linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, Bartlomiej Zolnierkiewicz , Kyungmin Park Subject: Re: [PATCH v2 1/5] misc: sensorhub: Add sensorhub driver Date: Mon, 24 Nov 2014 13:35:55 +0100 Message-ID: <5942877.97OQIAaJx7@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <547318E0.8070407@samsung.com> References: <1416593957-19788-1-git-send-email-k.wrona@samsung.com> <54707ECA.7090800@kernel.org> <547318E0.8070407@samsung.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:GSnoTS4ndy7NlHuQklhfMf7gnbclLLOrdocLJSvDEsF duHA94R0pui3PCezAjtvPIGkyc7qwhankcnsNb22Xri8+5slmn +6bod4Fq6NLoYiq4DBMALCSFFk77ax3+brQcgALqG6nJgK772K ujqAMwXAbTxoWweQT5gbWEypNpGUbkb6mMQTlgpmhZANxAeWe9 /JwSvQnnkHvy4qNc++0fCJyA/cNiYGJrD1uy2lQ31NxlE2cru0 wRg6gQYdu5Uf5kPp+W0Q+AXtiz3ia/UDj5Ss//L4xUzbhUmwSu yFyjis8fy03U9c5ODLLX67aZOM+LUpN5SLHwaEktdxV0vnaLdn FBYprReHf7GA+FpIM5s0= X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 24 November 2014 12:39:12 Karol Wrona wrote: > It is possible that it can serve as input device sth else. So you are > right about MFD. > > The structure of mfd directory is flat. I wonder what can be better: > just putting these sources inside mfd dir or to some new category inside mfd. > Generally sensorhub will not differ than others mfd devs but in the near future > it can be that we end up with different (sensor)hubs or in my case with one core > driver with several interfaces, mcu's modes - sth like ssp-i2c.c etc. > These drivers can grow in size as these devices will appear in different boards. You should be able to abstract the interface differences using regmap for the most part, so there would only be a small stub that is i2c or spi specific, and a lot of mfd drivers have that. > Also there is a question where firmware loader (stm32fwu) should be placed as it > is a library? Can you describe what this library does? Is this for loading firmware into device RAM or into flash? Does it always use USB? Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/