On Fri, Dec 4, 2015 at 4:33 PM, Geert Uytterhoeven <geert+rene...@glider.be> wrote:
> If the Renesas R-Car GPIO driver cannot find a functional clock, it > prints a warning, .e.g. > > gpio_rcar ffc40000.gpio: unable to get clock > > and continues, as the clock is optional, depending on the SoC type. > This warning may confuse users. > > To fix this, add a flag to indicate that the clock is mandatory or > optional: > - If the clock is mandatory (on R-Car Gen2 and Gen3), a missing clock > is now treated as a fatal error, > - If the clock is optional (on R-Car Gen1), the warning is no longer > printed. > > Suggested-by: Magnus Damm <magnus.d...@gmail.com> > Signed-off-by: Geert Uytterhoeven <geert+rene...@glider.be> > --- > v2: > - Use booleans instead of bitfields, > - Add reference to R-Car Gen3. Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
