[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141230221522.GO17565@valkosipuli.retiisi.org.uk>
Date: Wed, 31 Dec 2014 00:15:22 +0200
From: Sakari Ailus <sakari.ailus@....fi>
To: Jacek Anaszewski <j.anaszewski@...sung.com>
Cc: linux-leds@...r.kernel.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, kyungmin.park@...sung.com,
b.zolnierkie@...sung.com, pavel@....cz, cooloney@...il.com,
rpurdie@...ys.net, s.nawrocki@...sung.com, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
Lee Jones <lee.jones@...aro.org>,
Chanwoo Choi <cw00.choi@...sung.com>
Subject: Re: [PATCH/RFC v9 07/19] dt-binding: mfd: max77693: Add DT binding
related macros
Hi Jacek,
The driver depends on these so I'd rearrange this patch in the set before
the driver patch.
On Wed, Dec 03, 2014 at 05:06:42PM +0100, Jacek Anaszewski wrote:
> Add macros for max77693 led part related binding.
>
> Signed-off-by: Jacek Anaszewski <j.anaszewski@...sung.com>
> Acked-by: Kyungmin Park <kyungmin.park@...sung.com>
> Cc: Lee Jones <lee.jones@...aro.org>
> Cc: Chanwoo Choi <cw00.choi@...sung.com>
> ---
> include/dt-bindings/mfd/max77693.h | 38 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 include/dt-bindings/mfd/max77693.h
>
> diff --git a/include/dt-bindings/mfd/max77693.h b/include/dt-bindings/mfd/max77693.h
> new file mode 100644
> index 0000000..4011cb47
> --- /dev/null
> +++ b/include/dt-bindings/mfd/max77693.h
> @@ -0,0 +1,38 @@
> +/*
> + * This header provides macros for MAX77693 device binding
> + *
> + * Copyright (C) 2014, Samsung Electronics Co., Ltd.
> + *
> + * Author: Jacek Anaszewski <j.anaszewski@...sung.com>
> + */
> +
> +#ifndef __DT_BINDINGS_MAX77693_H__
> +#define __DT_BINDINGS_MAX77693_H
> +
> +/* External control pins */
> +#define MAX77693_LED_FLED_UNUSED 0
> +#define MAX77693_LED_FLED_USED 1
> +
> +/* FLED pins */
> +#define MAX77693_LED_FLED1 1
> +#define MAX77693_LED_FLED2 2
I'd personally simply use numbers for the above but I can't really say to be
an expert on the topic.
> +/* External trigger type */
> +#define MAX77693_LED_TRIG_TYPE_EDGE 0
> +#define MAX77693_LED_TRIG_TYPE_LEVEL 1
> +
> +/* Trigger flags */
> +#define MAX77693_LED_TRIG_FLASHEN (1 << 0)
> +#define MAX77693_LED_TRIG_TORCHEN (1 << 1)
> +#define MAX77693_LED_TRIG_SOFTWARE (1 << 2)
> +
> +#define MAX77693_LED_TRIG_ALL (MAX77693_LED_TRIG_FLASHEN | \
> + MAX77693_LED_TRIG_TORCHEN | \
> + MAX77693_LED_TRIG_SOFTWARE)
> +
> +/* Boost modes */
> +#define MAX77693_LED_BOOST_OFF 0
> +#define MAX77693_LED_BOOST_ADAPTIVE 1
> +#define MAX77693_LED_BOOST_FIXED 2
> +
> +#endif /* __DT_BINDINGS_MAX77693_H */
--
Regards,
Sakari Ailus
e-mail: sakari.ailus@....fi XMPP: sailus@...iisi.org.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists