mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v1] Revert "extcon: usb-gpio: add support for ACPI gpio interface"
Date: Wed, 22 Mar 2017 10:14:55 +0900	[thread overview]
Message-ID: <58D1D00F.40300@samsung.com> (raw)
In-Reply-To: <20170321183747.32450-1-andriy.shevchenko@linux.intel.com>

Hi,

On 2017년 03월 22일 03:37, Andy Shevchenko wrote:
> The commit 942c7924a51e introduced a check for ACPI handle for the
> device that never appears on any ACPI-enabled platform so far. It seems
> a confusion with extcon-intel-int3496 which does support ACPI-enabled
> platforms.

Only for the reason that there is no any usecase until now,
and remove the confusion between extcon-usb-gpio and extcon-intel-int3496.
Should we revert it? 

I think that both extcon-usb-gpio and extcon-intel-int3496
driver are not same operation perfectly. Also, the filename
of extcon-intel-int3496 has specific name. Instead, extcon-usb-gpio.c
is more common device driver.

Can the extcon-intel-int3496.c support the everything on acpi side?

> 
> Revert commit 942c7924a51e to avoid any confusion in the future.
> 
> Cc: Lu Baolu <baolu.lu@linux.intel.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/extcon/extcon-usb-gpio.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/extcon/extcon-usb-gpio.c b/drivers/extcon/extcon-usb-gpio.c
> index d47573a31e17..9c925b05b7aa 100644
> --- a/drivers/extcon/extcon-usb-gpio.c
> +++ b/drivers/extcon/extcon-usb-gpio.c
> @@ -26,7 +26,6 @@
>  #include <linux/platform_device.h>
>  #include <linux/slab.h>
>  #include <linux/workqueue.h>
> -#include <linux/acpi.h>
>  #include <linux/pinctrl/consumer.h>
>  
>  #define USB_GPIO_DEBOUNCE_MS	20	/* ms */
> @@ -111,7 +110,7 @@ static int usb_extcon_probe(struct platform_device *pdev)
>  	struct usb_extcon_info *info;
>  	int ret;
>  
> -	if (!np && !ACPI_HANDLE(dev))
> +	if (!np)
>  		return -EINVAL;
>  
>  	info = devm_kzalloc(&pdev->dev, sizeof(*info), GFP_KERNEL);
> 


-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

  reply	other threads:[~2017-03-22  1:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170321183839epcas2p1de828034e7360ea8ea365861b9335626@epcas2p1.samsung.com>
2017-03-21 18:37 ` Andy Shevchenko
2017-03-22  1:14   ` Chanwoo Choi [this message]
2017-03-22 13:09     ` Andy Shevchenko
2017-03-24 11:03       ` Chanwoo Choi
2017-03-24 11:24         ` Andy Shevchenko
2017-03-24 11:47           ` Chanwoo Choi
2017-03-27  0:51             ` Lu Baolu
2017-03-27  4:18   ` Chanwoo Choi
2017-03-27  7:07     ` Andy Shevchenko

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=58D1D00F.40300@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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