From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: Qualcomm APQ8060 DragonBoard ALS sensor
Date: Wed, 1 Feb 2017 10:36:31 -0800 [thread overview]
Message-ID: <20170201183631.GJ10531@minitux> (raw)
In-Reply-To: <20170131102114.25085-2-linus.walleij@linaro.org>
On Tue 31 Jan 02:21 PST 2017, Linus Walleij wrote:
> This adds the Capella CM3605 ambient light and proximity sensor
> to the APQ8060 DragonBoard device tree. Notice that we also set
> up pin config for the AOUT line and GPIO lines, and that we set
> the default trigger on the infrared LED to associate with the
> "cm3605" trigger so the IR LED is controlled by this the CM3605
> driver.
Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
[..]
> + mpps at 50 {
> + dragon_cm3605_mpps: cm3605-mpps {
> + pinconf {
> + pins = "mpp5";
> + function = "analog";
> + input-enable;
> + bias-high-impedance;
> + /* Let's use channel 5 */
> + qcom,amux-route = <PMIC_MPP_AMUX_ROUTE_CH5>;
Unrelated to this patch, I did look at how this works on later devices.
It seems like we want to be able to switch the amux-route depending on
which ADC "channel" we're querying - e.g. on DB820c we have thermistors
on 3 different AMUX inputs but we don't have 3 mpps available.
Any thoughts on how to deal with this?
> + power-source = <PM8058_GPIO_S3>;
> + };
> + };
> + };
Regards,
Bjorn
next prev parent reply other threads:[~2017-02-01 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 10:21 [PATCH 1/2] ARM: dts: add XOADC and IIO HWMON to MSM8660/APQ8060 Linus Walleij
2017-01-31 10:21 ` [PATCH 2/2] ARM: dts: Qualcomm APQ8060 DragonBoard ALS sensor Linus Walleij
2017-02-01 18:36 ` Bjorn Andersson [this message]
2017-02-03 13:05 ` Linus Walleij
2017-02-09 1:42 ` Bjorn Andersson
2017-02-21 15:44 ` Linus Walleij
2017-02-01 18:31 ` [PATCH 1/2] ARM: dts: add XOADC and IIO HWMON to MSM8660/APQ8060 Bjorn Andersson
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=20170201183631.GJ10531@minitux \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).