Thread (129 messages) 129 messages, 12 authors, 2020-11-30

Re: [PATCH 20/32] riscv: Add Kendryte K210 FPIOA pinctrl driver

From: Linus Walleij <hidden>
Date: 2020-11-29 21:34:40
Also in: linux-clk, linux-gpio, linux-riscv, linux-spi

On Tue, Nov 24, 2020 at 9:53 AM Damien Le Moal [off-list ref] wrote:
On 2020/11/24 17:43, Linus Walleij wrote:
quoted
Would also be nice if the maintainer could add some comments?
What do you mean ? I do not understand. scripts/get_maintainer.pl indicates that
you are the maintainer of the pinctrl drivers subsystem.
Sorry I thought we had a RISCV driver already, and we don't
so this is cool.
Do you mean adding an
entry to the MAINTAINER file for this driver ? I can do that and put my self as
maintainer. Or do you mean you would like a comment from Palmer (riscv arch
maintainer) ?
That would be nice. Whoever will enthusiastically review patches to
this driver and make sure it works and get modernized should ideally
be listed as maintainer. I suggest you list yourself.

The only input I want from the RISCV arch maintainer would
be on this code:

+/*
+ * Most devices on the K210 SoC depend on pin mapping changes to initialize
+ * correctly. So initialize this driver early as part of the post core
+ * initialization.
+ */
+static int __init k210_fpioa_init(void)
+{
+       return platform_driver_register(&k210_fpioa_driver);
+}
+postcore_initcall(k210_fpioa_init);

This is a bit nasty and we do not recommend it. But I will accept it
if the arch maintainer claims it is necessary. What happens if you
just make it initialize at driver level?

Yours,
Linus Walleij
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help