All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	Maciej Purski <m.purski@samsung.com>,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, b.zolnierkie@samsung.com,
	dri-devel@lists.freedesktop.org, robh+dt@kernel.org,
	krzk@kernel.org
Subject: Re: [PATCH 1/2] drm/bridge: add Silicon Image SiI9234 driver
Date: Mon, 14 Aug 2017 17:35:45 +0100	[thread overview]
Message-ID: <20170814163545.ofhjvl4tk7imeozm@sirena.org.uk> (raw)
In-Reply-To: <35788498.IS2VIdUVsa@avalon>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

On Fri, Aug 11, 2017 at 12:00:43PM +0300, Laurent Pinchart wrote:

> (now CC'ing Mark Brown with his correct e-mail address)

This is a *lot* of quoted discussion...

> > Okay, I see no problem adding support for all those three supplies, but
> > I was wondering how to model them in the device tree, because from the
> > software perspective ALL power supplies needed by this chip are enabled by a
> > single GPIO line switch.

> > I see 3 possible solutions:
> > 1. Keep only single vcc supply for now and use fixed gpio regulator for it
> > as a provider. Add a comment that it fact it provides 3 different power
> > signals.
> > 2. Extend fixed gpio regulator driver and bindings so it will be possible to
> > have more than one fixed regulator controlled by the same gpio pin.
> > 3. Model VCC_3.3V_MHL and VCC_1.8V_MHL providers as "vctrl-regulator" and
> > use this VSIL_1.2 as control voltage for them.

> > Which one do you prefer?

> 2 would be best I think, but that's more work. Mark, what do you think ?

Just model them all individually and let the regulator framework sort it
out.  It's got the concept of shared GPIO enables already so you should
be able to just describe the system directly and the framework will
figure things out, and even if it didn't there should be no need to
change any of the bindings here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-08-14 16:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170803074535eucas1p107414859fa54647d1f623c73d0fc17f2@eucas1p1.samsung.com>
2017-08-03  7:45 ` [PATCH 0/2] add Silicon Image SiI9234 driver Maciej Purski
     [not found]   ` <CGME20170803074538eucas1p1fec88e4f2c3ebc00054fd362a504c03e@eucas1p1.samsung.com>
2017-08-03  7:45     ` [PATCH 1/2] drm/bridge: " Maciej Purski
2017-08-03 10:24       ` Laurent Pinchart
2017-08-04  6:55         ` Marek Szyprowski
2017-08-10 14:51           ` Laurent Pinchart
2017-08-11  7:00             ` Marek Szyprowski
2017-08-11  8:59               ` Laurent Pinchart
2017-08-11  9:00               ` Laurent Pinchart
2017-08-14 16:35                 ` Mark Brown [this message]
2017-08-03 19:36       ` kbuild test robot
     [not found]         ` <1501746323-5254-2-git-send-email-m.purski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2017-08-03 19:36           ` [PATCH] drm/bridge: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-08-12 22:43           ` [PATCH 1/2] drm/bridge: add Silicon Image SiI9234 driver kbuild test robot
     [not found]   ` <CGME20170803074541eucas1p2b054d4853a98819fc42f19f7cae7f419@eucas1p2.samsung.com>
2017-08-03  7:45     ` [PATCH 2/2] ARM: dts: exynos: Add HDMI and Sil9234 to Trats2 board Maciej Purski
2017-08-03 19:20       ` Krzysztof Kozlowski
2017-08-04  6:32         ` Marek Szyprowski
2017-08-04  6:44           ` Krzysztof Kozlowski

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=20170814163545.ofhjvl4tk7imeozm@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.purski@samsung.com \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.