linux-kernel - Re: [PATCH v5] usb:serial:pl2303: add GPIOs interface on PL2303

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140729164058.GA2440@udknight>
Date:	Wed, 30 Jul 2014 00:40:59 +0800
From:	Wang YanQing <udknight@...il.com>
To:	Andreas Mohr <andi@...as.de>
Cc:	gregkh@...uxfoundation.org, linus.walleij@...aro.org,
	jhovold@...il.com, dforsi@...il.com, gnomes@...rguk.ukuu.org.uk,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] usb:serial:pl2303: add GPIOs interface on PL2303

On Fri, Jul 25, 2014 at 09:53:23PM +0200, Andreas Mohr wrote:
> Hi,
> 
> On Sat, Jul 26, 2014 at 01:35:23AM +0800, Wang YanQing wrote:
> 
> > +         It support 2 GPIOs on PL2303HX currently,
> "supports"
> 

Right!

> > +static u8 gpio_dir_mask[GPIO_NUM] = {0x10, 0x20};
> > +static u8 gpio_value_mask[GPIO_NUM] = {0x40, 0x80};
> 
> Those two should better be static const, too (sorry).
> You're at v5 already (wow, what endurance!),
> but if there ever will be a v6... :)
> 

OK! there will be v6.

> > +static int pl2303_gpio_startup(struct usb_serial *serial)
> > +{
> > +	struct pl2303_serial_private *spriv = usb_get_serial_data(serial);
> > +	char *label;
> > +	int ret;
> > +	int minor;
> > +
> > +	if (spriv->type != &pl2303_type_data[TYPE_HX])
> > +		return 0;
> 
> Hmm, that's some structurally inverted check code.
> The pl2303_gpio_startup() function in its entirety
> is specific to the GPIO-supporting type TYPE_HX,
> thus we shouldn't even *call* a type-specific sub handler
> if we know that we're a different chip type.
> And in fact pl2303_startup() already has everything in place
> for a direct type check.
> Yeah, that might be "less reliable" than a type check planted within
> pl2303_gpio_startup() (someone might bogusly call pl2303_gpio_startup()
> for a different-type chip),

This is just caller vs callee check, and ether of them
has itself advantage in fit situation. I don't think
it is wrong to reuse current pl2303_type_data for type
check in pl2303_gpio_startup just like I don't think 
it is wrong to do the check prior to call pl2303_gpio_starutp
in you suggestion.

> but such an unrelated (external!) type check dependency
> shouldn't be interwoven with a type-specific setup helper
> which is to be concerned with inner-layer setup handling only.

It is not unrelated type check, type-specific setup helper
has right to check whether it is the "really" specified type.:)

> A probably(!) even better idea here might be
> to add some function pointers to spriv->type struct def,
> to be able to do != NULL ptr checks and in such cases
> call such chip-specific setup functions (i.e., call the HX type helper
> which internally knows that it needs to do GPIO setup).

I don't think pl2303_type_data is right place to hold it,
pl2303_type_data is right place for serial concerning function,
not for gpio.

> Such a change might be able to get rid of several #ifdef:s, too...

#ifdef is still necessary, most people don't need this feature,
it bring no benefit to make kernel image bigger.

> (plus, provide long-lasting generic infrastructure for future chip types).

A simple and specified device driver, I doubt the need for
so "generic infrastructure", and current code could just work
for future chip types, just looks like below:

if (type == HX ||
    type == "future type"||
    more future type)
pl2303_gpio_startup();

Thanks for review, and sorry for my delay reply.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/