Hi Jacopo,
On Wed, Sep 5, 2018 at 5:30 PM Jacopo Mondi <[email protected]> wrote:
> This patch adds VIN{4,5} pins, groups and functions to the R8A77990 SoC.
>
> Signed-off-by: Jacopo Mondi <[email protected]>
Thanks for your patch!
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a77990.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a77990.c
> +/* - VIN5
> ------------------------------------------------------------------- */
> +static const union vin_data vin5_data_a_pins = {
> + .data16 = {
Please note that union vin_data has space for 24 entries, so the last 8
are unused. We have several other drivers doing this, though, also
for .data12, and it is still a win, compared to duplicating the arrays.
We might want to introduce vin_data16 and vin_data12 unions in the
future, to avoid the unused entries. But for now, this is fine.
> + RCAR_GP_PIN(1, 1), RCAR_GP_PIN(1, 2),
> + RCAR_GP_PIN(1, 19), RCAR_GP_PIN(1, 12),
> + RCAR_GP_PIN(1, 15), RCAR_GP_PIN(1, 16),
> + RCAR_GP_PIN(1, 17), RCAR_GP_PIN(1, 18),
> + RCAR_GP_PIN(0, 12), RCAR_GP_PIN(0, 13),
> + RCAR_GP_PIN(0, 9), RCAR_GP_PIN(0, 11),
> + RCAR_GP_PIN(0, 8), RCAR_GP_PIN(0, 10),
> + RCAR_GP_PIN(0, 2), RCAR_GP_PIN(0, 3),
> + },
> +};
> +static const union vin_data vin5_data_b_pins = {
> + .data8 = {
This one...
> + RCAR_GP_PIN(2, 23), RCAR_GP_PIN(0, 4),
> + RCAR_GP_PIN(0, 7), RCAR_GP_PIN(0, 12),
> + RCAR_GP_PIN(0, 13), RCAR_GP_PIN(0, 14),
> + RCAR_GP_PIN(0, 16), RCAR_GP_PIN(0, 17),
> + },
> +};
> +
> +static const union vin_data vin5_data_b_mux = {
> + .data8 = {
... and this one are definitely a loss, as there are 16 unused entries, and
you don't use or need the union feature...
> + VI5_DATA0_B_MARK, VI5_DATA1_B_MARK,
> + VI5_DATA2_B_MARK, VI5_DATA3_B_MARK,
> + VI5_DATA4_B_MARK, VI5_DATA5_B_MARK,
> + VI5_DATA6_B_MARK, VI5_DATA7_B_MARK,
> + },
> +};
> @@ -1889,6 +2077,32 @@ static const struct sh_pfc_pin_group pinmux_groups[] =
> {
> SH_PFC_PIN_GROUP(usb0_id),
> SH_PFC_PIN_GROUP(usb30),
> SH_PFC_PIN_GROUP(usb30_id),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 8),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 10),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 12),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 16),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 20),
> + VIN_DATA_PIN_GROUP(vin4_data_a, 24),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 8),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 10),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 12),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 16),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 20),
> + VIN_DATA_PIN_GROUP(vin4_data_b, 24),
> + SH_PFC_PIN_GROUP(vin4_sync),
> + SH_PFC_PIN_GROUP(vin4_field),
> + SH_PFC_PIN_GROUP(vin4_clkenb),
> + SH_PFC_PIN_GROUP(vin4_clk),
> + VIN_DATA_PIN_GROUP(vin5_data_a, 8),
> + VIN_DATA_PIN_GROUP(vin5_data_a, 10),
> + VIN_DATA_PIN_GROUP(vin5_data_a, 12),
> + VIN_DATA_PIN_GROUP(vin5_data_a, 16),
> + VIN_DATA_PIN_GROUP(vin5_data_b, 8),
... here. So please revert the union change for this group.
> + SH_PFC_PIN_GROUP(vin5_sync_a),
> + SH_PFC_PIN_GROUP(vin5_field_a),
> + SH_PFC_PIN_GROUP(vin5_clkenb_a),
> + SH_PFC_PIN_GROUP(vin5_clk_a),
> + SH_PFC_PIN_GROUP(vin5_clk_b),
> };
>
> static const char * const avb_groups[] = {
> @@ -1996,6 +2210,40 @@ static const char * const usb30_groups[] = {
> "usb30_id",
> };
>
> +static const char * const vin4_groups[] = {
> + "vin4_data8_a",
> + "vin4_data10_a",
> + "vin4_data12_a",
> + "vin4_data16_a",
> + "vin4_data20_a",
> + "vin4_data24_a",
> + "vin4_data8_b",
> + "vin4_data10_b",
> + "vin4_data12_b",
> + "vin4_data16_b",
> + "vin4_data20_b",
> + "vin4_data24_b",
> + "vin4_data8_sft8",
You dropped the sft8 pins, but forgot to remove the sft8 group name.
> + "vin4_sync",
> + "vin4_field",
> + "vin4_clkenb",
> + "vin4_clk",
> +};
> +
> +static const char * const vin5_groups[] = {
> + "vin5_data8_a",
> + "vin5_data8_sft8_a",
Likewise.
> + "vin5_data10_a",
> + "vin5_data12_a",
> + "vin5_data16_a",
> + "vin5_data8_b",
> + "vin5_sync_a",
> + "vin5_field_a",
> + "vin5_clkenb_a",
> + "vin5_clk_a",
> + "vin5_clk_b",
> +};
The rest looks OK to me, and matches the datasheet clarification.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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