Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751559AbdF0FhZ (ORCPT ); Tue, 27 Jun 2017 01:37:25 -0400 Received: from nblzone-211-213.nblnetworks.fi ([83.145.211.213]:34876 "EHLO hillosipuli.retiisi.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751312AbdF0FhR (ORCPT ); Tue, 27 Jun 2017 01:37:17 -0400 Date: Tue, 27 Jun 2017 08:36:42 +0300 From: Sakari Ailus To: "H. Nikolaus Schaller" Cc: Hugues Fruchet , Sylwester Nawrocki , Guennadi Liakhovetski , Rob Herring , Mark Rutland , Maxime Coquelin , Alexandre Torgue , Mauro Carvalho Chehab , Hans Verkuil , devicetree , linux-arm-kernel , LKML , linux-media@vger.kernel.org, Benjamin Gaignard , Yannick Fertre Subject: Re: [PATCH v1 2/6] [media] ov9650: add device tree support Message-ID: <20170627053642.GW12407@valkosipuli.retiisi.org.uk> References: <1498143942-12682-1-git-send-email-hugues.fruchet@st.com> <1498143942-12682-3-git-send-email-hugues.fruchet@st.com> <20170626163102.GQ12407@valkosipuli.retiisi.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1170 Lines: 33 On Mon, Jun 26, 2017 at 07:46:34PM +0200, H. Nikolaus Schaller wrote: > Hi, > > > Am 26.06.2017 um 18:31 schrieb Sakari Ailus : > > > > Hi Hugues, > > > > On Thu, Jun 22, 2017 at 05:05:38PM +0200, Hugues Fruchet wrote: > >> @@ -1545,15 +1577,22 @@ static int ov965x_remove(struct i2c_client *client) > >> } > >> > >> static const struct i2c_device_id ov965x_id[] = { > >> - { "OV9650", 0 }, > >> - { "OV9652", 0 }, > >> + { "OV9650", 0x9650 }, > >> + { "OV9652", 0x9652 }, > > > > This change does not appear to match with the patch description nor it the > > information is used. How about not changing it, unless there's a reason to? > > The same for the data field of the of_device_id array below. > > I think it could/should be used to check if the camera chip that is found > by reading the product-id and version registers does match what the device > tree expects and abort probing on a mismatch. Makes sense. But it should be a separate patch, shouldn't it? You could also put the id to the ops struct, and choose the ops struct that way. Entirely up to you. -- Sakari Ailus e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk