From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: defconfig: enable HDMI output for RCar
Date: Wed, 14 Oct 2015 07:54:04 +0000 [thread overview]
Message-ID: <CAMuHMdVRBvZbM-nGWu1NA67vqXASzox2SnJUw2H0fcn7PcwjEQ@mail.gmail.com> (raw)
In-Reply-To: <1407974835-11064-1-git-send-email-khilman@linaro.org>
Hi Magnus,
On Wed, Oct 14, 2015 at 9:44 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> On Wed, Oct 14, 2015 at 4:07 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> On Wed, Oct 14, 2015 at 3:09 AM, Laurent Pinchart
>> <laurent.pinchart@ideasonboard.com> wrote:
>>>> Tested with a Lager board and using both I2C/IIC. Based on my testings in
>>>> Dublin with a Koelsch board, I'd be very surprised if it fails with Koelsch.
>>>> Laurent may prove me wrong ;)
>>>
>>> I've tried to reproduce the problem tonight and couldn't, even without your
>>> recent i2c-rcar patches :-/ I'll keep running tests on Koelsch with that
>>> configuration and make sure to report any issue I can find.
>>
>> The Koelsch that failed has a much newer U-Boot (b653737dfca2), which
>> only enables the MSTP clocks that are really needed, while you and I have
>> much older versions (I have b6af5fcc8dfc).
>
> With the new CPG-MSSR driver it should be possible to disable unused
> MSTP clocks in the kernel during boot without too much trouble, right?
> Of course it is not something that is needed right away, but DT
> architecture wise it seems possible to squeeze that in without having
> to update the DT binding.
Unused clocks are already disabled by the clock framework, but that
happens at late_initcall() time, i.e. after i2c probing.
Or do you mean disabling them upfront?
There are some clocks that must not be disabled. Some of them are not
documented.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-10-14 7:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 0:07 [PATCH] ARM: shmobile: defconfig: enable initrd and atag dtb compat Kevin Hilman
2014-08-14 5:25 ` Simon Horman
2014-08-17 0:37 ` Simon Horman
2014-08-14 23:03 ` [PATCH] ARM: shmobile: defconfig: enable ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND Simon Horman
2014-08-17 0:38 ` Simon Horman
2015-10-10 19:14 ` [PATCH] ARM: shmobile: defconfig: enable HDMI output for RCar Wolfram Sang
2015-10-12 0:19 ` Simon Horman
2015-10-12 6:38 ` Wolfram Sang
2015-10-13 1:03 ` Simon Horman
2015-10-14 1:09 ` Laurent Pinchart
2015-10-14 5:52 ` Wolfram Sang
2015-10-14 7:07 ` Geert Uytterhoeven
2015-10-14 7:44 ` Magnus Damm
2015-10-14 7:54 ` Geert Uytterhoeven [this message]
2015-10-14 8:09 ` Magnus Damm
2015-10-14 8:22 ` Geert Uytterhoeven
2015-10-14 8:25 ` Wolfram Sang
2015-10-14 8:36 ` Magnus Damm
2015-10-14 11:41 ` Laurent Pinchart
2015-10-14 12:11 ` Khiem Nguyen
2015-10-14 12:55 ` Laurent Pinchart
2015-10-14 13:18 ` Khiem Nguyen
2015-10-14 13:32 ` Geert Uytterhoeven
2015-10-14 14:11 ` Khiem Nguyen
2015-11-30 13:35 ` [PATCH] ARM: shmobile: defconfig: Enable CONFIG_PRINTK_TIME Geert Uytterhoeven
2015-12-01 6:44 ` Simon Horman
2015-12-09 9:28 ` Geert Uytterhoeven
2015-12-10 7:04 ` Simon Horman
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=CAMuHMdVRBvZbM-nGWu1NA67vqXASzox2SnJUw2H0fcn7PcwjEQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-sh@vger.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 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).