LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] ARM: dts: tpc: Device tree description of the iMX6Q TPC board
Date: Thu, 5 Apr 2018 11:16:44 -0300 [thread overview]
Message-ID: <CAOMZO5DHtvX64oseDFsLGiYmQPcb3thUrGeLxX8dgp69vUNZMg@mail.gmail.com> (raw)
In-Reply-To: <20180405070939.22245-1-lukma@denx.de>
Hi Lukasz,
On Thu, Apr 5, 2018 at 4:09 AM, Lukasz Majewski <lukma@denx.de> wrote:
> + reg_audio: regulator-audio {
> + compatible = "regulator-fixed";
> + regulator-name = "sgtl5000-supply";
> + gpio = <&gpio6 31 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-always-on;
> + };
sgtl5000 has 3 supplies: VDDD, VDDIO, VDDA.
Which supply does this reg_audio supply to the chip?
Can't you use any of the existing sgtl5000 regulator bindings to
describe this supply?
next prev parent reply other threads:[~2018-04-05 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 7:09 Lukasz Majewski
2018-04-05 14:16 ` Fabio Estevam [this message]
2018-04-05 14:42 ` Lukasz Majewski
2018-04-05 15:02 ` Fabio Estevam
2018-04-10 10:37 ` [PATCH v4] " Lukasz Majewski
2018-04-10 20:32 ` [PATCH v5] " Lukasz Majewski
2018-04-18 3:55 ` Shawn Guo
2018-04-19 14:32 ` [PATCH v6] " Lukasz Majewski
2018-04-20 1:06 ` Rob Herring
2018-04-23 8:48 ` Shawn Guo
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=CAOMZO5DHtvX64oseDFsLGiYmQPcb3thUrGeLxX8dgp69vUNZMg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--subject='Re: [PATCH v3] ARM: dts: tpc: Device tree description of the iMX6Q TPC board' \
/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
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).