Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754774AbbEUHTI (ORCPT ); Thu, 21 May 2015 03:19:08 -0400 Received: from mail-oi0-f47.google.com ([209.85.218.47]:35041 "EHLO mail-oi0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754613AbbEUHTC (ORCPT ); Thu, 21 May 2015 03:19:02 -0400 MIME-Version: 1.0 In-Reply-To: <20150520145227.GA3787@ulmo.nvidia.com> References: <1430761002-9327-1-git-send-email-abrestic@chromium.org> <1430761002-9327-5-git-send-email-abrestic@chromium.org> <20150513143954.GA3394@x1> <55544CC5.9050001@nvidia.com> <20150514074058.GA22418@x1> <20150520063551.GD3627@x1> <20150520145227.GA3787@ulmo.nvidia.com> Date: Thu, 21 May 2015 09:19:00 +0200 Message-ID: Subject: Re: [PATCH v8 4/9] mfd: Add binding document for NVIDIA Tegra XUSB From: Linus Walleij To: Thierry Reding Cc: Lee Jones , Andrew Bresticker , Jon Hunter , Stephen Warren , Alexandre Courbot , "devicetree@vger.kernel.org" , "linux-tegra@vger.kernel.org" , "linux-usb@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Samuel Ortiz Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1221 Lines: 46 On Wed, May 20, 2015 at 4:52 PM, Thierry Reding wrote: > I'm a little confused by the simple-mfd approach. The only code I see in > linux-next for this is a single line that adds the "simple-mfd" string > to the OF device ID table in drivers/of/platform.c. As far as I can tell > this will merely cause child devices to be created. There won't be a > shared regmap and resources won't be set up properly either. That is correct. The simple-mfd is a two-component approach. Ideally, in the simplest case, you combine simple-mfd with syscon. foo@0 { compatible = "foo", "syscon", "simple-mfd"; reg = <0x10000000 0x1000>; bar@1 { compatible = "bar"; }; baz@2 { compatible = "baz"; }; }; This will instantiate bar and baz. These subdrivers then probe and: probe() { struct regmap *map; map = syscon_node_to_regmap(parent->of_node); (...) } Simple, syscon is the MFD hub. Yours, Linus Walleij -- 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/