linux-kernel - Re: [PATCH 4/6] extcon: arizona: Add device binding for second jack detect pin on GPIO5

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150925091042.GD5432@ck-lbox>
Date:	Fri, 25 Sep 2015 10:10:42 +0100
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	Chanwoo Choi <cw00.choi@...sung.com>
CC:	<lee.jones@...aro.org>, <robh+dt@...nel.org>, <pawel.moll@....com>,
	<mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>,
	<galak@...eaurora.org>, <myungjoo.ham@...sung.com>,
	<sameo@...ux.intel.com>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/6] extcon: arizona: Add device binding for second
 jack detect pin on GPIO5

On Fri, Sep 25, 2015 at 09:54:26AM +0900, Chanwoo Choi wrote:
> Hi Charles,
> 
> I have one comment.
> I think current extcon-arizona.c has the many platform data
> so, extcon-arizona.c use the too much if statement to support each feature
> for different wolfsonmicro codec. I think it cause the complicated code.
> 
> For example,
> You may use 'struct of_device_id' as following. You used already this method
> on drivers/mfd/arizona-core.c. If you separate the function of each wmXXXX arizona,
> it makes improved readability for extcon-arizona.c and some user will use extcon-arizora
> more easily.
> 
> struct arizona_extcon_data {
> 	void (*init)(...);
> 	void (*irq_handler)(...);
> 	...	
> };
> 
> struct arizona_extcon_data wm8994_data {
> 	.init = wm8994_extcon_init,
> 	.irq_handler = wm8994_extcon_irq_handler;
> 	...
> };
> 
> static const struct of_device_id arizona_extcon_dt_match[] = {
> 	{
> 		.compatible = "wm8994-arizona-extcon",
> 		.data = (void *)wm8994_data;
> 	}, {
> 		.compatible = "wmXXXX-arizona-extcon",
> 		.data = (void *)wmXXXX_data;
> 	}, 
> };
> 
> I expect that you will revise the arizona-extcon.c driver on next time.

I will have an investigation to see what ideas I can come up with
here and send through some patches.

But I am slightly worried you think the gains will be better than
they actually will be. Most of the platform data is just that
platform data, and needs to be configured based on the system not
based on the CODEC.

Thanks,
Charles
--
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/