[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b5d2d914-0c2b-4cd1-b894-f894a93a54f9@moroto.mountain>
Date: Wed, 5 Jun 2024 10:22:49 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Dmitry Yashin <dmt.yashin@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Heiko Stuebner <heiko@...ech.de>,
Luca Ceresoli <luca.ceresoli@...tlin.com>,
Jianqun Xu <jay.xu@...k-chips.com>, Jonas Karlman <jonas@...boo.se>,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] pinctrl: rockchip: add rk3308b SoC support
On Tue, Jun 04, 2024 at 07:10:20PM +0500, Dmitry Yashin wrote:
> Add pinctrl support for rk3308b. This pin controller much the same as
> rk3308's, but with additional iomux routes and 3bit iomuxes selected
> via gpio##_sel_src_ctrl registers. Set them up in the function
> rk3308b_soc_sel_src_init to use new 3bit iomuxes over some 2bit old
> ones and update iomux_recalced and iomux_routes for the new SoC's.
>
> Fixes: 1f3e25a06883 ("pinctrl: rockchip: fix RK3308 pinmux bits")
Why does this one have a Fixes tag? Isn't this new hardware support?
Possibly patch 1/2 was not actually a fix but just preparation for this
patch?
regards,
dan carpenter
> Signed-off-by: Dmitry Yashin <dmt.yashin@...il.com>
> Reviewed-by: Luca Ceresoli <luca.ceresoli@...tlin.com>
Powered by blists - more mailing lists