From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thierry Reding Date: Wed, 01 Oct 2014 07:41:40 +0000 Subject: Re: [linux-sunxi] Re: [PATCH 4/4] simplefb: add clock handling code Message-Id: <20141001074139.GB18463@ulmo> MIME-Version: 1 Content-Type: multipart/mixed; boundary="U+BazGySraz5kW0T" List-Id: References: <20140902092508.GR15297@lukather> <20140927235601.19023.31593@quantum> <20140929080637.GB12506@ulmo> <20140929092301.GC4388@lukather> <20140929101805.GB26008@ulmo> <20140929114643.GB4081@lukather> <20140929134708.GB30998@ulmo> <20140929155517.GR16977@sirena.org.uk> <20140930050923.GB29874@ulmo> <20140930173928.GH4273@sirena.org.uk> In-Reply-To: <20140930173928.GH4273@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org --U+BazGySraz5kW0T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 30, 2014 at 06:39:28PM +0100, Mark Brown wrote: > On Tue, Sep 30, 2014 at 07:09:24AM +0200, Thierry Reding wrote: > > On Mon, Sep 29, 2014 at 04:55:17PM +0100, Mark Brown wrote: >=20 > > > So long as we're ensuring that when we don't start supporting resourc= es > > > without DT additions or at least require DT additions to actively man= age > > > them (which can then include simplefb hookup) we should be fine. >=20 > > I'm not sure I understand what you mean. If we add a driver for the PMIC > > that exposes these regulators and then add a DT node for the PMIC, we'd > > still need to fix the firmware to generate the appropriate DT properties > > to allow simplefb to enable the regulators. >=20 > No, you don't. It's only if you start describing the regulators in the > PMIC in DT that you run into problems. Unconfigured regulators won't be > touched. Okay, that's what I meant. It seems rather odd to add a PMIC DT node but omit the description of the regulators that it exposes. Unless the regulators are truly unused, as in not connected to any peripherals. > > So unless firmware is updated at the same time, regulators will get > > disabled because they are unused. >=20 > That won't happen unless the regulators are explicitly described, if > they are described as unused then this will of course happen. With described as unused you mean they have a node in DT, so constraints are applied and all that, but no driver actually uses them? The fundamental issue is that if we start describing simplefb nodes with an incomplete set of resources then we're bound to run into problems where it'll break once these new resources are described in the DTS. If the simplefb node was described in the DTS then this would be less of a problem because the resources could be added to the simplefb node at the same time. However given that simplefb is supposed to be generated by firmware this is no longer possible. It will inevitably break unless you upgrade the DTB and the firmware at the same time. And it was already decided long ago that upgrading the firmware should never be a requirement for keeping things working. I don't see any way to prevent that other than ignoring the resources in simplefb completely. Thierry --U+BazGySraz5kW0T Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUK7AzAAoJEN0jrNd/PrOhNCcP/i2fvGNms6dF6hbWldZJUGM1 6XfFKWRUDy6o8rWuti6GkKe059AikCDZnwmq1OXJyadTMzK7jYsgbksfA4Ekdt+g K0xCBa78SwQMuXKEryJ9Sd+9x711vWbIA+MNClyaY4AAzhJf/oKDpzcCHIlh69kQ JL3SbMsqh8AtAncZsIyEn0/usCLIocNAct2zBLpy3f0HJPNwwDdXrQVygkXWtdps NFGO72/yr2/+UYsPK/QYRUMYxQur4jGDnB2kqof8R64pM0MxJ+0eHhhVrdkrDc99 XWqiKZaXFsstUqNskAghccuy1mIC72jNfLrotfapQpxCUWfdZW50oZolHfht37fr k+giMsk3NjCh0sKK8LPEHQgcYE8rjY/h5UBY0mnAEWvVxoFLJ3jWQFaD6Q2F3Fd6 ILVHUzQrVPAEPpAlzHKkCIBS/GVYg02JjlkSPQgu5MejyqpdLO6v8MJZ6mKiTd0d grkWkQ44bLCI7z+tdAzYwbGQHEgpYpTWrErSGKeuLlcwcfq9M0iKQAT+i3BsF7Zg 1oO2JbvLjVCkO+hSs1PC27n3G0jiwUpd+IZ1hIS4LS62EsQ9KKcTiz4pg4baUphz fhH2ne6lA1PYUhYAbykTVm7gepWcypOgOZgD+ef7nTmLrpZ9Ri2hULPsXAAZNDWd vuIKxzi8J550UrMy1PLl =/TUH -----END PGP SIGNATURE----- --U+BazGySraz5kW0T--