From: Lee Jones <lee.jones@linaro.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Ramakrishna Pallala <ramakrishna.pallala@intel.com>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH v9] extcon-axp288: Add axp288 extcon driver support
Date: Thu, 30 Apr 2015 10:30:29 +0100 [thread overview]
Message-ID: <20150430093029.GA1815@x1> (raw)
In-Reply-To: <5541DC33.80400@samsung.com>
On Thu, 30 Apr 2015, Chanwoo Choi wrote:
> Hi Ram,
>
> This patch has still one minor issue on below comment.
> But I fix it and will apply it on extcon-next branch
> after discussing how to apply this patch with Lee Jones (MFD maintainer).
>
> Dear Lee,
> Do you want to send pull request after I make the immutable branch
> for this patch? or apply this patch on extcon git without any pull request?
Let's try without the pull-request.
> On 05/01/2015 12:14 AM, Ramakrishna Pallala wrote:
> > This patch adds the extcon support for AXP288 PMIC which
> > has the BC1.2 charger detection capability. Additionally
> > it also adds the USB mux switching support b/w SOC and PMIC
> > based on GPIO control.
> >
> > Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
> > Acked-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > drivers/extcon/Kconfig | 7 +
> > drivers/extcon/Makefile | 1 +
> > drivers/extcon/extcon-axp288.c | 385 ++++++++++++++++++++++++++++++++++++++++
> > include/linux/mfd/axp20x.h | 5 +
> > 4 files changed, 398 insertions(+)
> > create mode 100644 drivers/extcon/extcon-axp288.c
> >
>
> [snip]
>
> > + vbus_attach ? EXTCON_GPIO_MUX_SEL_SOC
> > + : EXTCON_GPIO_MUX_SEL_PMIC);
> > +
> > + atomic_notifier_call_chain(&info->otg->notifier,
> > + vbus_attach ? USB_EVENT_VBUS : USB_EVENT_NONE, NULL);
> > + }
> > +
> > + if (notify_charger)
> > + extcon_set_cable_state(info->edev, cable, vbus_attach);
> > +
> > + /* Clear the flags on disconnect event */
> > + if (!vbus_attach)
> > + notify_otg = notify_charger = false;
> > +
> > + return 0;
> > +
> > +dev_det_ret:
> > + if (ret < 0)
> > + dev_err(info->dev, "BC Mod detection error\n");
>
> You miss the fix about following comment.
> "BC Mod detection error\n" -> "failed to detect BC Mod\n"
>
> [snip]
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2015-04-30 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:14 [PATCH v9] extcon-axp288: Add axp288 extcon driver support Ramakrishna Pallala
2015-04-30 7:39 ` Chanwoo Choi
2015-04-30 7:43 ` Pallala, Ramakrishna
2015-04-30 9:30 ` Lee Jones [this message]
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=20150430093029.GA1815@x1 \
--to=lee.jones@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ramakrishna.pallala@intel.com \
--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