Hi Wolfram,
On Tue, Aug 12, 2014 at 11:47 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
> On Tue, Aug 12, 2014 at 03:11:18PM +0200, Geert Uytterhoeven wrote:
>> On r8a7790, DT device nodes and C/DT pinmux data for IIC<n> are called
>> "iic<n>", with DT aliases from "i2c<m>" to the "iic<n>" DT nodes.
>> On r8a7791, DT device nodes and C/DT pinmux data for IIC<n> are called
>> "i2c<m>", with DT aliases from "i2c<m>" to the "i2c<m>" DT nodes.
>>
>> In light of the proliferation of other members of the R-Car Gen 2 families, is
>> there a plan to make this consistent?
>
> The 'i2c'-prefix describes the IP core handled by the rcar driver. This
> core is named i2c in the datasheets.
>
> The 'iic'-prefix describes the IP core handled by the sh-mobile-driver.
> This core is named iic(b) in the datasheets.
I know the difference between i2c and iic(b).
However, the DT device nodes and C/DT pinmux data for iic(b) on r8a7791
are called i2c, too, instead of iic.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
