[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191112132811.p6xgmxp7co6ugkkn@ti.com>
Date: Tue, 12 Nov 2019 07:28:11 -0600
From: Benoit Parrot <bparrot@...com>
To: Sakari Ailus <sakari.ailus@....fi>
CC: Hans Verkuil <hverkuil@...all.nl>, <linux-media@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [Patch v2 12/20] media: ti-vpe: cal: Add DRA76x support
Benoit Parrot <bparrot@...com> wrote on Wed [2019-Nov-06 14:58:39 -0600]:
> Sakari Ailus <sakari.ailus@....fi> wrote on Wed [2019-Nov-06 10:57:09 +0200]:
> > Hi Benoit,
> >
> > On Mon, Nov 04, 2019 at 01:31:32PM -0600, Benoit Parrot wrote:
> >
> > ...
> >
> > > +static struct cal_data dra76x_cal_data = {
> >
> > const?
>
> Hmm, most likely.
Well, it turns out they cannot be constified because we need to be able to
update the register offset fir the regmap used for the syscon object.
So I'll leave them as is.
Benoit
>
> >
> > > + .csi2_phy_core = dra76x_cal_csi_phy,
> > > + .num_csi2_phy = ARRAY_SIZE(dra76x_cal_csi_phy),
> > > +
> >
> > This newline seems extra.
> >
> > > + .flags = 0,
> >
> > And flags will be zero in any case, as one more struct members are assigned
> > to.
>
> Is this guaranteed or compiler version dependent?
>
> >
> > > +};
> >
> > --
> > Regards,
> >
> > Sakari Ailus
Powered by blists - more mailing lists