Received: by 10.192.165.148 with SMTP id m20csp2139903imm; Thu, 26 Apr 2018 06:39:53 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/2+puxE/WufHG46A1dFTi5ySxB9HwBPy26Ue/EJ9VPVLNXMm+6AOg/2wMY5NainuzWO97J X-Received: by 10.99.127.86 with SMTP id p22mr27800638pgn.306.1524749993727; Thu, 26 Apr 2018 06:39:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524749993; cv=none; d=google.com; s=arc-20160816; b=VnmbN6ZQaZ+KtiuSxZ1hZqMkeq127lHc5ok5eqfYtJFjKN1FzqAjomCg1N141DIE5z ssds/5bLm8RtUL6oP/V58FcGG9rb1GT3H0x5eGBkjmp/2ncdhCQCgi0GRfIF39Poreo7 2MHfjRuIoLltCaOuX/Rla0gfPw9TTvzz72exThPg7cZCaLhdimLBoZPDH0gKk1F/XGrO lJ9LCRELIC4wuaThKRsCYfky3lmc5+roqaYdApr6q72kp07aIVXFC4a9ajxTM7/j+onP sfcCmftxzjnHOHowv4oPXB7FiKx9ImDRH4bUEy8Z8djePcb/9DPN8sqJBCiJA0Ymyxsu At4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=PPs1emqgd9VnDhli8/LOTVLd7upAkV0GGSMGxFL1mKs=; b=oKD6Da3VKqnCC8PHvqMHoZU9COf8axm0vsG5kIjqFjzYZ68ey2qHC5rRTwR8uWxEzQ Sp18wiX29G5fzEtQp/a2q8yuYdEkX/59q4gCIz39RqqGMr3ZZuFCuhd+NQQOv12MUbxC K0G/cgyZlJC72LhnM3dWv01cvmwEIcDwj/vCyJ7Nek2qnEfVQxZ0GLXcVI54eXVbQqWa UHZpfW+3L60bvewvmGFYziNfQKfwZgei6zhgkCEd5UP5nRS9O/7xOsWwR72pMAD1rwlp lAQOUDn/+Fg/rpTvqk5BrucAkmkBTDvym4hl4DXXGgSij03Rn76qqeyjjUPUGTp5Prbe P4iw== 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 w61-v6si18798079plb.155.2018.04.26.06.39.39; Thu, 26 Apr 2018 06:39:53 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756384AbeDZNhB (ORCPT + 99 others); Thu, 26 Apr 2018 09:37:01 -0400 Received: from bert.emutex.com ([91.103.1.109]:55050 "EHLO bert.emutex.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755172AbeDZNg7 (ORCPT ); Thu, 26 Apr 2018 09:36:59 -0400 Received: from [92.51.199.138] (helo=statler.emutex.com) by bert.emutex.com with esmtp (Exim 4.84) (envelope-from ) id 1fBh5b-0002Zc-Jz; Thu, 26 Apr 2018 14:37:35 +0100 Received: from [79.140.212.107] (helo=localhost) by statler.emutex.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84) (envelope-from ) id 1fBh4w-0003Gu-9t; Thu, 26 Apr 2018 14:36:55 +0100 Date: Thu, 26 Apr 2018 14:36:53 +0100 From: Javier Arteaga To: Lee Jones Cc: Linus Walleij , Dan O'Donovan , Andy Shevchenko , Mika Westerberg , Heikki Krogerus , Jacek Anaszewski , Pavel Machek , linux-gpio@vger.kernel.org, linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH RESEND 3/3] pinctrl: upboard: Add UP2 pinctrl and gpio driver Message-ID: <20180426133653.4yhjv6uuaox7vt7m@localhost> References: <20180421085009.28773-1-javier@emutex.com> <20180421085009.28773-4-javier@emutex.com> <20180426065028.fvdf7ke5va2kacmv@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180426065028.fvdf7ke5va2kacmv@dell> X-Spam-Score: -1.0 (-) X-Spam-Report: Spam detection software, running on the system "statler.emutex.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Thu, Apr 26, 2018 at 07:50:28AM +0100, Lee Jones wrote: > > static const struct mfd_cell upboard_up2_mfd_cells[] = { > > + { .name = "upboard-pinctrl" }, > > UPBOARD_LED_CELL(upboard_up2_led_data, 0), > > UPBOARD_LED_CELL(upboard_up2_led_data, 1), > > UPBOARD_LED_CELL(upboard_up2_led_data, 2), > > Please made this a separate patch. > > There aren't any build dependencies between the files. [...] Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 26, 2018 at 07:50:28AM +0100, Lee Jones wrote: > > static const struct mfd_cell upboard_up2_mfd_cells[] = { > > + { .name = "upboard-pinctrl" }, > > UPBOARD_LED_CELL(upboard_up2_led_data, 0), > > UPBOARD_LED_CELL(upboard_up2_led_data, 1), > > UPBOARD_LED_CELL(upboard_up2_led_data, 2), > > Please made this a separate patch. > > There aren't any build dependencies between the files. Will do. I have one further question about MFD in this patch too - should I keep passing regmap into the driver via dev_get_drvdata(pdev->dev.parent), or is explicit platform_data preferable? Andy suggested platform_data allows more flexibility on the parent device side (although I can't see upboard-pinctrl being used other than as a child of the upboard driver). I went with parent drvdata simply because that's what I found in other MFD drivers and material [1]. Thank you! [1]: http://events17.linuxfoundation.org/sites/events/files/slides/belloni-mfd-regmap-syscon_0.pdf