devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Maciej Purski <m.purski@samsung.com>
Cc: linux-kernel@vger.kernel.org,
	"Chanwoo Choi" <cw00.choi@samsung.com>,
	lee.jones@linaro.org,
	"Bartłomiej Żołnierkiewicz" <b.zolnierkie@samsung.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3] mfd: max77693: Add muic of_compatible in mfd_cell
Date: Tue, 22 Aug 2017 14:01:13 +0200	[thread overview]
Message-ID: <CAJKOXPeJeMOgQB32ajWT15TLHw6h8cxnf5UFT-dturCfarxv0g@mail.gmail.com> (raw)
In-Reply-To: <1503387537-18342-1-git-send-email-m.purski@samsung.com>

On Tue, Aug 22, 2017 at 9:38 AM, Maciej Purski <m.purski@samsung.com> wrote:
> This patch adds muic of_compatible in order to use the muic device
> driver in device tree.
>
> v2:
> - added muic to documentation

Change log should not go to commit message. Put it after separator ---.

+cc devicetree - scripts/get_maintainer.pl should point you that list.

With the change in commit msg:
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>

Best regards,
Krzysztof

>
> v3:
> - removed duplication
>
> Signed-off-by: Maciej Purski <m.purski@samsung.com>
> ---
>  Documentation/devicetree/bindings/mfd/max77693.txt | 6 ++++++
>  drivers/mfd/max77693.c                             | 5 ++++-
>  2 files changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/max77693.txt b/Documentation/devicetree/bindings/mfd/max77693.txt
> index 6a1ae3a..e675497 100644
> --- a/Documentation/devicetree/bindings/mfd/max77693.txt
> +++ b/Documentation/devicetree/bindings/mfd/max77693.txt
> @@ -127,6 +127,12 @@ Required properties for the LED child node:
>  Optional properties for the LED child node:
>  - label : see Documentation/devicetree/bindings/leds/common.txt
>
> +Optional nodes:
> +- max77693-muic :
> +       Node used only by extcon consumers.
> +       Required properties:
> +               - compatible : "maxim,max77693-muic"
> +
>  Example:
>  #include <dt-bindings/leds/common.h>
>
> diff --git a/drivers/mfd/max77693.c b/drivers/mfd/max77693.c
> index 662ae0d..1c05ea0 100644
> --- a/drivers/mfd/max77693.c
> +++ b/drivers/mfd/max77693.c
> @@ -48,7 +48,10 @@ static const struct mfd_cell max77693_devs[] = {
>                 .name = "max77693-charger",
>                 .of_compatible = "maxim,max77693-charger",
>         },
> -       { .name = "max77693-muic", },
> +       {
> +               .name = "max77693-muic",
> +               .of_compatible = "maxim,max77693-muic",
> +       },
>         {
>                 .name = "max77693-haptic",
>                 .of_compatible = "maxim,max77693-haptic",
> --
> 2.7.4
>

           reply	other threads:[~2017-08-22 12:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1503387537-18342-1-git-send-email-m.purski@samsung.com>]

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=CAJKOXPeJeMOgQB32ajWT15TLHw6h8cxnf5UFT-dturCfarxv0g@mail.gmail.com \
    --to=krzk@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.purski@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;
as well as URLs for NNTP newsgroup(s).