From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga01.intel.com ([192.55.52.88]:15665 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754777AbbCRWOE (ORCPT ); Wed, 18 Mar 2015 18:14:04 -0400 Message-ID: <5509F87D.9060603@linux.intel.com> Date: Thu, 19 Mar 2015 00:13:17 +0200 From: Sakari Ailus MIME-Version: 1.0 To: Lad Prabhakar , Laurent Pinchart , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Mauro Carvalho Chehab , Hans Verkuil CC: LMML , LKML , devicetree@vger.kernel.org Subject: Re: [PATCH v7] media: i2c: add support for omnivision's ov2659 sensor References: <1426628910-11927-1-git-send-email-prabhakar.csengg@gmail.com> In-Reply-To: <1426628910-11927-1-git-send-email-prabhakar.csengg@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Hi Prabhakar, Lad Prabhakar wrote: ... > +static int ov2659_g_volatile_ctrl(struct v4l2_ctrl *ctrl) > +{ > + struct ov2659 *ov2659 = > + container_of(ctrl->handler, struct ov2659, ctrls); > + struct v4l2_mbus_framefmt *fmt = &ov2659->format; > + > + switch (ctrl->id) { > + case V4L2_CID_PIXEL_RATE: > + if (fmt->code != MEDIA_BUS_FMT_SBGGR8_1X8) > + ov2659->link_frequency->val = > + ov2659->pdata->link_frequency / 2; > + else > + ov2659->link_frequency->val = > + ov2659->pdata->link_frequency; You should simply use v4l2_ctrl_s_ctrl_int64() in ..._set_fmt() as this isn't really a proper volatile control, but its value depends on the format. -- Sakari Ailus sakari.ailus@linux.intel.com