Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751605AbdHQKDO (ORCPT ); Thu, 17 Aug 2017 06:03:14 -0400 Received: from mail-wr0-f182.google.com ([209.85.128.182]:35131 "EHLO mail-wr0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751015AbdHQKCL (ORCPT ); Thu, 17 Aug 2017 06:02:11 -0400 Date: Thu, 17 Aug 2017 11:02:06 +0100 From: Lee Jones To: Scott Branden Cc: Greg Kroah-Hartman , BCM Kernel Feedback , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Shreesha Rajashekar Subject: Re: [PATCH 3/3] mfd: d1w: iproc: Add d1w driver Message-ID: <20170817100206.tqb5kluje6nr27ob@dell> References: <1502905525-5646-1-git-send-email-scott.branden@broadcom.com> <1502905525-5646-4-git-send-email-scott.branden@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1502905525-5646-4-git-send-email-scott.branden@broadcom.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 787 Lines: 28 On Wed, 16 Aug 2017, Scott Branden wrote: > From: Shreesha Rajashekar > > d1w bus master controller is added as a mfd node. Why? > ds1wm driver is hooked to this node through the mfd framework. Why? What makes this an MFD device? > Signed-off-by: Shreesha Rajashekar > Signed-off-by: Scott Branden > --- > drivers/mfd/Kconfig | 11 +++ > drivers/mfd/Makefile | 1 + > drivers/mfd/bcm-iproc-d1w.c | 202 ++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 214 insertions(+) > create mode 100644 drivers/mfd/bcm-iproc-d1w.c -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog