From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <1562576868-8124-1-git-send-email-yoshihiro.shimoda.uh@renesas.com> <1562576868-8124-3-git-send-email-yoshihiro.shimoda.uh@renesas.com> In-Reply-To: <1562576868-8124-3-git-send-email-yoshihiro.shimoda.uh@renesas.com> From: Geert Uytterhoeven Date: Tue, 6 Aug 2019 11:23:41 +0200 Message-ID: Subject: Re: [PATCH RFC 2/7] pinctrl: sh-pfc: remove incomplete flag "cfg->type" Content-Type: text/plain; charset="UTF-8" To: Yoshihiro Shimoda Cc: Linus Walleij , Geert Uytterhoeven , Thierry Reding , Rob Herring , Mark Rutland , "open list:GPIO SUBSYSTEM" , Linux PWM List , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux-Renesas List-ID: Hi Shimoda-san, On Mon, Jul 8, 2019 at 11:08 AM Yoshihiro Shimoda wrote: > The old commit c58d9c1b26e3 ("sh-pfc: Implement generic pinconf > support") broke the cfg->type flag to PINMUX_TYPE_FUNCTION because > sh_pfc_pinconf_set() didn't call sh_pfc_reconfig_pin(). > Now if we fix the cfg->type condition, it gets worse because: > - Some drivers might be deferred so that .set_mux() will be called > multiple times. > - In such the case, the sh-pfc driver returns -EBUSY even if > the group is the same, and then that driver fails to probe. > > Since the pinctrl subsystem already has such conditions according > to @set_mux and @gpio_request_enable, this patch just remove > the incomplete flag from sh-pfc/pinctrl.c. Do we need to set sh_pfc_pinmux_ops.strict = true? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org 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