Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752662AbbDCLYK (ORCPT ); Fri, 3 Apr 2015 07:24:10 -0400 Received: from nblzone-211-213.nblnetworks.fi ([83.145.211.213]:46309 "EHLO hillosipuli.retiisi.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751953AbbDCLYG (ORCPT ); Fri, 3 Apr 2015 07:24:06 -0400 Date: Fri, 3 Apr 2015 14:23:56 +0300 From: Sakari Ailus To: Pavel Machek Cc: Andrew Morton , pali.rohar@gmail.com, sre@debian.org, sre@ring0.de, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, galak@codeaurora.org, bcousson@baylibre.com, m.chehab@samsung.com, devicetree@vger.kernel.org Subject: Re: [PATCHv3] media: i2c/adp1653: devicetree support for adp1653 Message-ID: <20150403112355.GJ20756@valkosipuli.retiisi.org.uk> References: <20150402143846.GA11687@amd> <20150402161453.GH20756@valkosipuli.retiisi.org.uk> <20150402203043.GB29963@amd> <20150402234823.GI20756@valkosipuli.retiisi.org.uk> <20150403082344.GA14721@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150403082344.GA14721@amd> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1600 Lines: 53 Hi Pavel, On Fri, Apr 03, 2015 at 10:23:44AM +0200, Pavel Machek wrote: > Hi! > > > Hi Pawel, > > I'm still Pavel. v, not w. I know too many Pawels. Sorry about that. :-) > > > > > Hi Pawel, > > > > > A corresponding change to the N900 dts would be very nice. > > > > > > Corresponding change to the dts will come in separate patch. Or do you > > > have n900 for testing? > > > > Yes, it should be a separate patch, I agree. > > > > I do have one but I can't say when I'd have time to test it. I'm fine with > > you having tested it though. > > > > > > I think you're missing change to adp1653_i2c_driver.driver.of_match_table. > > > > > > It actually worked for me, which means device tree somehow does it > > > magic. > > > > By magic? :-) It probably just ends up comparing the device and the driver > > names. How about adding the of_match_table? > > I guess it uses adp1653_id_table. I'd hade to add redundand > information, because if it would just mask the errors if the code > changed... Indeed, that's true. This is comparing "adp1653" vs. comparing "adi,adp1653". I think I still prefer the latter since it's got also the vendor prefix included. Suppose we change this later and someone misspelled the vendor prefix --- their board would break. -- Regards, Sakari Ailus e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk -- 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/