From: Lee Jones <lee.jones@linaro.org>
To: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Cc: linux-kernel@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Carlo Caione <carlo@caione.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH v3 1/2] mfd/axp20x: add support for extcon cell
Date: Wed, 8 Apr 2015 10:49:34 +0100 [thread overview]
Message-ID: <20150408094934.GE5162@x1> (raw)
In-Reply-To: <1428513134-31402-2-git-send-email-ramakrishna.pallala@intel.com>
When submitting patches, please observe the $SUBJECT line formatting
of the subsystem you're sending to.
You can do so by: `git log --oneline -- drivers/<subsystem>`
In the case of MFD it's:
mfd: <device>: <Description>
Note the ':' separators and the capitalisation of the first letter of
the description string.
> This patch adds the mfd cell info for axp288 extcon device.
>
> Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
> ---
> drivers/mfd/axp20x.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
Nevertheless, patch applied, thanks.
> diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
> index b1b580a..4c8e0e9 100644
> --- a/drivers/mfd/axp20x.c
> +++ b/drivers/mfd/axp20x.c
> @@ -290,6 +290,29 @@ static struct resource axp288_adc_resources[] = {
> },
> };
>
> +static struct resource axp288_extcon_resources[] = {
> + {
> + .start = AXP288_IRQ_VBUS_FALL,
> + .end = AXP288_IRQ_VBUS_FALL,
> + .flags = IORESOURCE_IRQ,
> + },
> + {
> + .start = AXP288_IRQ_VBUS_RISE,
> + .end = AXP288_IRQ_VBUS_RISE,
> + .flags = IORESOURCE_IRQ,
> + },
> + {
> + .start = AXP288_IRQ_MV_CHNG,
> + .end = AXP288_IRQ_MV_CHNG,
> + .flags = IORESOURCE_IRQ,
> + },
> + {
> + .start = AXP288_IRQ_BC_USB_CHNG,
> + .end = AXP288_IRQ_BC_USB_CHNG,
> + .flags = IORESOURCE_IRQ,
> + },
> +};
> +
> static struct resource axp288_charger_resources[] = {
> {
> .start = AXP288_IRQ_OV,
> @@ -345,6 +368,11 @@ static struct mfd_cell axp288_cells[] = {
> .resources = axp288_adc_resources,
> },
> {
> + .name = "axp288_extcon",
> + .num_resources = ARRAY_SIZE(axp288_extcon_resources),
> + .resources = axp288_extcon_resources,
> + },
> + {
> .name = "axp288_charger",
> .num_resources = ARRAY_SIZE(axp288_charger_resources),
> .resources = axp288_charger_resources,
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-04-08 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 17:12 [PATCH v3 0/2] Add extcon support for AXP288 PMIC Ramakrishna Pallala
2015-04-08 17:12 ` [PATCH v3 1/2] mfd/axp20x: add support for extcon cell Ramakrishna Pallala
2015-04-08 9:49 ` Lee Jones [this message]
2015-04-08 9:56 ` Pallala, Ramakrishna
2015-04-08 17:12 ` [PATCH v3 2/2] extcon-axp288: Add axp288 extcon driver support Ramakrishna Pallala
2015-04-24 4:27 ` Chanwoo Choi
2015-04-27 10:44 ` Pallala, Ramakrishna
2015-04-27 10:59 ` Chanwoo Choi
2015-04-27 13:19 ` Pallala, Ramakrishna
2015-04-27 14:16 ` Chanwoo Choi
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=20150408094934.GE5162@x1 \
--to=lee.jones@linaro.org \
--cc=carlo@caione.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