On 12/01/17 09:56, Sebastian Hesselbarth wrote: > On 01/11/2017 03:44 PM, Linus Walleij wrote: >> On Fri, Jan 6, 2017 at 5:15 AM, Chris Packham >> <chris.packham@xxxxxxxxxxxxxxxxxxx> wrote: >> >>> From: Kalyan Kinthada <kalyan.kinthada@xxxxxxxxxxxxxxxxxxx> >>> >>> This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs >>> from Marvell. >>> >>> Signed-off-by: Kalyan Kinthada <kalyan.kinthada@xxxxxxxxxxxxxxxxxxx> >>> Signed-off-by: Chris Packham <chris.packham@xxxxxxxxxxxxxxxxxxx> >> >> I am waiting for an ACK or comment from the maintainers on >> this patch. Sebastian? > > Sorry for the ignorance. > > I don't have the patch to reply to inline, but: > > - In the driver MPP_MODE2, spi0 there is a typo "csk" instead of "sck". > - MPP_MODE5 binding "dev","bootcs" and driver "dev","bootcs0" differ. > - MPP_MODE6 binding "gpio" and driver "gpo" differ. > - MPP_MODE17 binding "dev","clk" and driver "dev","clkout" differ. > - MPP_MODE19 binding mentiones "dev","rb" but driver does not. > - MPP_MODE20 binding "gpio" and driver "gpo" differ. > - MPP_MODE20 binding "dev","we" and driver "dev","we0" differ. > - MPP_MODE21 through MPP_MODE30 binding "gpio" and driver "gpo" differ. > - remove spaces before "0, 0" in mv98dx3236_mpp_gpio_ranges. > > Most of it is cosmetic stuff, so if you fix it feel free to add my > > Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@xxxxxxxxx> Hi Sebastian, Hopefully I can get a v4 out with the above fixed soon. One point on "gpio" vs "gpo" this one isn't a typo. Some of these pins can be driven as outputs but can't be used as inputs. From a pinctrl driver point of view there is no difference but I did want to convey that from a system design point of view if you really need something to be an input you shouldn't use one of these pins. This is also noted in the datasheets so it doesn't necessarily need repeating. If you still want me to use "gpio" in the code and binding I'm happy to do so. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
