From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7][ 3/5] video: mx3fb: Introduce regulator support.
Date: Mon, 17 Mar 2014 06:20:26 +0000 [thread overview]
Message-ID: <20140317062026.GZ17250@pengutronix.de> (raw)
In-Reply-To: <1394788369-5096-3-git-send-email-denis@eukrea.com>
[Added Mark to Cc]
On Fri, Mar 14, 2014 at 10:12:47AM +0100, Denis Carikli wrote:
>
> + of_property_read_string(display_np, "regulator-name",
> + ®ulator_name);
> +
[...]
> + /* In dt mode,
> + * using devm_regulator_get would require that the proprety referencing
> + * the regulator phandle has to be inside the mx3fb node.
> + */
> + if (np) {
> + if (regulator_name)
> + mx3fbi->reg_lcd = regulator_get(NULL, regulator_name);
> +
> + if (IS_ERR(mx3fbi->reg_lcd))
> + return PTR_ERR(mx3fbi->reg_lcd);
> + } else {
> + /* Permit that driver without a regulator in non-dt mode */
> + mx3fbi->reg_lcd = regulator_get(dev, "lcd");
> + }
This patch adds regulator support for the display of a i.MX3 IPU. The
problem Denis has to solve here is that he needs to get the regulator,
but the display devicenode doesn't have a struct device associated with
it, so he cannot provide one to regulator_get(). One way out here could
be a of_regulator_get(struct device_node *). Mark, would this be ok with
you?
(Of course a proper driver for the display would be nicer, but this
would immediately bring us to some Common display framework, something
which is being worked on quite a while now without success)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-03-17 6:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 9:12 [PATCH v7][ 1/5] video: mx3fb: Use devm_kzalloc Denis Carikli
2014-03-14 9:12 ` [PATCH v7][ 2/5] video: mx3fb: Add device tree suport Denis Carikli
2014-03-14 9:12 ` [PATCH v7][ 3/5] video: mx3fb: Introduce regulator support Denis Carikli
2014-03-14 9:23 ` [PATCH v7][ 3/5] video: mx3fb: Introduce =?UTF-8?B?cmVndWxhdG9yIHN1c Alexander Shiyan
2014-03-14 11:23 ` [PATCH v7][ 3/5] video: mx3fb: Introduce regulator support Denis Carikli
2014-03-14 12:38 ` [PATCH v7][ 3/5] video: mx3fb: Introduce =?UTF-8?B?cmVndWxhdG9yIHN1c Alexander Shiyan
2014-03-17 6:20 ` Sascha Hauer [this message]
2014-06-10 13:29 ` [PATCH v7][ 3/5] video: mx3fb: Introduce regulator support Denis Carikli
2014-08-22 22:00 ` Mark Brown
2014-06-19 6:58 ` Denis Carikli
2014-03-14 9:12 ` [PATCH v7][ 4/5] ARM: dts: i.MX35: Add display support Denis Carikli
2014-03-14 9:12 ` =?UTF-8?q?=5BPATCH=20v7=5D=5B=205/5=5D=20ARM=3A=20dts=3A=20mbimxsd35=20Add=20video=20and=20displays= Denis Carikli
2014-05-08 10:31 ` [PATCH v7][ 1/5] video: mx3fb: Use devm_kzalloc Tomi Valkeinen
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=20140317062026.GZ17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).