From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030624AbbKDPfq (ORCPT ); Wed, 4 Nov 2015 10:35:46 -0500 Received: from bear.ext.ti.com ([192.94.94.41]:39540 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932688AbbKDPfn (ORCPT ); Wed, 4 Nov 2015 10:35:43 -0500 Subject: Re: [PATCH v4 4/5] regulator: tps65912: Add regulator driver for the TPS65912 PMIC To: Mark Brown References: <1443731874-21362-1-git-send-email-afd@ti.com> <1443731874-21362-5-git-send-email-afd@ti.com> <20151022164724.GZ8232@sirena.org.uk> CC: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Lee Jones , Alexandre Courbot , Grygorii Strashko , , From: "Andrew F. Davis" Message-ID: <563A25BE.90609@ti.com> Date: Wed, 4 Nov 2015 09:35:26 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151022164724.GZ8232@sirena.org.uk> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/22/2015 11:47 AM, Mark Brown wrote: > On Thu, Oct 01, 2015 at 03:37:53PM -0500, Andrew F. Davis wrote: > >> +static const struct of_device_id tps65912_regulator_of_match_table[] = { >> + { .compatible = "ti,tps65912-regulator", }, >> + { /* sentinel */ }, >> +}; >> +MODULE_DEVICE_TABLE(of, tps65912_regulator_of_match_table); > > Does this IP block exist outside of the tps65912? If not why is it > directly represented in DT? It seems like this is describing how Linux > loads drivers not how the hardware is constructed but DT should describe > the hardware. > Something I just noticed, when I remove this table, module loading stops working, even with 'MODULE_ALIAS("platform:tps65912-regulator");'. It looks like when DT is enabled platform_uevent (drivers/base/platform.c:787) only sends out the OF MODALIAS event then returns, not sending out the platform event, is this desired behavior? If so then I will need this table even though I still create the device and match it on platform name as you suggested.