mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	lee.jones@linaro.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	myungjoo.ham@samsung.com, sameo@linux.intel.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] extcon: arizona: Add device binding for second jack detect pin on GPIO5
Date: Fri, 25 Sep 2015 09:54:26 +0900	[thread overview]
Message-ID: <56049B42.7030509@samsung.com> (raw)
In-Reply-To: <1442397404-7579-5-git-send-email-ckeepax@opensource.wolfsonmicro.com>

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.

Thanks,
Chanwoo Choi

On 2015년 09월 16일 18:56, Charles Keepax wrote:
> Some Arizona devices have the option to use the GPIO5 pin as a second
> jack detection pin. This patch adds device bindings to specify to the
> driver that it should use this pin. Note that the second jack detection
> pin is hard wired in the chip so can only be enabled through the
> binding, rather than a pin being specified.
> 
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
> ---
>  drivers/extcon/extcon-arizona.c |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/extcon/extcon-arizona.c b/drivers/extcon/extcon-arizona.c
> index dc1910d..992f80e 100644
> --- a/drivers/extcon/extcon-arizona.c
> +++ b/drivers/extcon/extcon-arizona.c
> @@ -1235,6 +1235,11 @@ static int arizona_extcon_device_get_pdata(struct arizona *arizona)
>  
>  	device_property_read_u32(arizona->dev, "wlf,gpsw", &pdata->gpsw);
>  
> +	pdata->jd_gpio5 = device_property_read_bool(arizona->dev,
> +						    "wlf,use-jd-gpio");
> +	pdata->jd_gpio5_nopull = device_property_read_bool(arizona->dev,
> +						"wlf,use-jd-gpio-nopull");
> +
>  	return 0;
>  }
>  
> 


  reply	other threads:[~2015-09-25  0:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  9:56 [PATCH 0/6] Arizona Extcon Update Device Bindings Charles Keepax
2015-09-16  9:56 ` [PATCH 1/6] extcon: arizona: Add device binding to enable ADC mode micdet Charles Keepax
2015-09-25  0:54   ` Chanwoo Choi
2015-09-16  9:56 ` [PATCH 2/6] extcon: arizona: Add device binding for the general purpose switch Charles Keepax
2015-09-25  0:54   ` Chanwoo Choi
2015-09-16  9:56 ` [PATCH 3/6] extcon: arizona: Add device binding for jack detect polarity inversion Charles Keepax
2015-09-16  9:56 ` [PATCH 4/6] extcon: arizona: Add device binding for second jack detect pin on GPIO5 Charles Keepax
2015-09-25  0:54   ` Chanwoo Choi [this message]
2015-09-25  9:10     ` Charles Keepax
2015-09-27  4:50       ` Chanwoo Choi
2015-09-16  9:56 ` [PATCH 5/6] mfd: arizona: Update DT binding documentation for mic detection Charles Keepax
2015-09-20  4:16   ` Lee Jones
2015-09-16  9:56 ` [PATCH 6/6] mfd: arizona: Update DT binding documentation for jack detection Charles Keepax
2015-09-20  4:17   ` Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56049B42.7030509@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome