On Wed, 4 Nov 2015 08:30:14 -0800
Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote:
> Hi Arnd,
>
> On Fri, Oct 30, 2015 at 09:27:03AM +0100, Arnd Bergmann wrote:
> > On Tuesday 27 October 2015 17:50:24 Jens Kuske wrote:
> > >
> > > +static int sun8i_h3_bus_reset_xlate(struct reset_controller_dev *rcdev,
> > > + const struct of_phandle_args *reset_spec)
> > > +{
> > > + unsigned int index = reset_spec->args[0];
> > > +
> > > + if (index < 96)
> > > + return index;
> > > + else if (index < 128)
> > > + return index + 32;
> > > + else if (index < 160)
> > > + return index + 64;
> > > + else
> > > + return -EINVAL;
> > > +}
> > > +
> > >
> >
> > This looks like you are doing something wrong and should either
> > put the actual number into DT,
>
> This is the actual number, except that there's some useless registers
> in between. Allwinner documents it like that:
>
> 0x0 Reset 0
> 0x4 Reset 1
> 0xc Reset 2
>
> So we have to adjust the offset to account with the blank register in
> between (0x8).
>
> > or use a two-cell representation, with the first cell indicating the
> > block (0, 1 or 2), and the second cell the index.
>
> And the missing register is not a block either.
>
> That would also imply either changing the bindings of that driver (and
> all the current DTS that are using it), or introducing a whole new
> driver just to deal with some extraordinary offset calculation.
In the H3, the holes are not used, but what would occur if these holes
would be used for some other purpose in future SoCs? Double mapping?
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
