[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbi0bS0yiJ9ac6Z44os0w6FyKm+UsvbgQEYzYKymjww-w@mail.gmail.com>
Date: Fri, 15 Sep 2023 11:02:01 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: "larry.lai" <larry.lai@...jingtech.com>
Cc: lee@...nel.org, andriy.shevchenko@...ux.intel.com, pavel@....cz,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-leds@...r.kernel.org, GaryWang@...on.com.tw,
musa.lin@...jingtech.com, jack.chang@...jingtech.com,
noah.hung@...jingtech.com
Subject: Re: [PATCH V6 2/3] pinctrl: Add support pin control for UP board CPLD/FPGA
On Fri, Sep 15, 2023 at 5:12 AM larry.lai <larry.lai@...jingtech.com> wrote:
> The UP Squared board <http://www.upboard.com> implements certain
> features (pin control) through an on-board FPGA.
>
> Reported-by: kernel test robot <lkp@...el.com>
> Signed-off-by: Gary Wang <garywang@...on.com.tw>
> Signed-off-by: larry.lai <larry.lai@...jingtech.com>
This v6 overall looks good to me!
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
Can the patch be merged on its own?
> +#include "core.h"
> +#include "intel/pinctrl-intel.h"
Didn't notice this before. But if Andy is OK with it, I'm
OK with it, I guess there is a reason? Perhaps it warrants
a comment explaining why you do this?
Valid reasons:
- You are using Intel-specific HW features also found in this
FPGA
Invalid reasons:
- Using nifty macros or helpers, then either make them generic
or (if they are small) duplicate them.
If it was that thing I asked Andy to keep locally because I didn't
agree with its generic usefulness, maybe I should be told to
reconsider.
Yours,
Linus Walleij
Powered by blists - more mailing lists