On Tue, May 24, 2016 at 05:53:34PM +0200, Krzysztof Kozlowski wrote:
>> Which devm_clk_get() error are you talking about? The one with susp_clk?
> Now I saw your original report on Debian bugzilla. Let's stick to v4.5.
I'm actually developing on 4.6, but sure. The differences are small from what
I
On 05/24/2016 05:26 PM, Steinar H. Gunderson wrote:
> On Tue, May 24, 2016 at 05:06:43PM +0200, Krzysztof Kozlowski wrote:
>> I looked quickly through the thread and I am not sure what is exactly
>> your problem.
>
> My immediate problem is that the repeated (deferred) probing is causing so
> much
On Tue, May 24, 2016 at 05:26:38PM +0200, Steinar H. Gunderson wrote:
> On Tue, May 24, 2016 at 05:06:43PM +0200, Krzysztof Kozlowski wrote:
> > Please send an appropriate separate patch for fixing this. Your email
> > did not reach people, I think.
> I only sent one patch so far, namely the leak
On Tue, May 24, 2016 at 05:06:43PM +0200, Krzysztof Kozlowski wrote:
> What other problems exactly do you have? Late binding of S2MPS11
> regulator driver? That does not look like a problem. If it is built as
> a module then it should be loaded, probably from initramfs because
> these are regulato
On Tue, May 24, 2016 at 05:06:43PM +0200, Krzysztof Kozlowski wrote:
> I looked quickly through the thread and I am not sure what is exactly
> your problem.
My immediate problem is that the repeated (deferred) probing is causing so
much logging that the system doesn't actually boot. The root cause
On Mon, May 23, 2016 at 7:06 PM, Steinar H. Gunderson
wrote:
> On Mon, May 23, 2016 at 05:24:55PM +0100, Mark Brown wrote:
Cc-ing Mark in case he has any insights (I hope I have the right email
address).
>> But nobody who works on probe deferral or made any of the suggestions I
>> mentio
On Mon, May 23, 2016 at 07:46:43PM +0200, Steinar H. Gunderson wrote:
> On Mon, May 23, 2016 at 07:06:17PM +0200, Steinar H. Gunderson wrote:
> > Then, there's the issue of why the messages come for each deferred probe
> > attempt. It seems from your message this is about something in the
> > decl
On Mon, May 23, 2016 at 07:06:17PM +0200, Steinar H. Gunderson wrote:
> On Mon, May 23, 2016 at 05:24:55PM +0100, Mark Brown wrote:
> >>> Cc-ing Mark in case he has any insights (I hope I have the right email
> >>> address).
> > But nobody who works on probe deferral or made any of the suggestion
On Mon, May 23, 2016 at 07:06:17PM +0200, Steinar H. Gunderson wrote:
> Then, there's the issue of why the messages come for each deferred probe
> attempt. It seems from your message this is about something in the
> declaration of the device tree; I don't understand the nuances here, but I
> suppos
On Mon, May 23, 2016 at 05:24:55PM +0100, Mark Brown wrote:
>>> Cc-ing Mark in case he has any insights (I hope I have the right email
>>> address).
> But nobody who works on probe deferral or made any of the suggestions I
> mentioned in the message you linked to, nor anyone who works on the
> driv
On Mon, May 23, 2016 at 04:40:47PM +0200, Steinar H. Gunderson wrote:
> On Mon, May 23, 2016 at 03:47:37PM +0200, Steinar H. Gunderson wrote:
> > In this case, it's not just an annoyance, though; they're so many that they
> > keep the system from booting unless loglevel is turned down. Cc-ing Mark
On Mon, May 23, 2016 at 03:47:37PM +0200, Steinar H. Gunderson wrote:
> I don't understand entirely why it tries 2000+ times before it succeeds
Now I do; the initramfs doesn't include i2c-exynos5, and before that is
loaded, s2mps11 (the regulator) can't come up either.
So fixing initramfs-tools t
On Sat, May 21, 2016 at 04:43:08PM +0200, Steinar H. Gunderson wrote:
> I still have this problem.
>
> I've noticed that somehow, there's a huge amount of USB PHYs being
> autodetected;
> probably related to this issue.
>
> sesse@soldroid:~$ ls -ld /sys/devices/platform/usb_phy* | wc -l
> 42
On Wed, 2016-05-11 at 01:49 +0200, Steinar H. Gunderson wrote:
> On Thu, May 05, 2016 at 11:29:18PM +0200, Steinar H. Gunderson wrote:
> >
> > I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid
> > and
> > installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself,
On Thu, May 05, 2016 at 11:29:18PM +0200, Steinar H. Gunderson wrote:
> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid
> and
> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating
> boot.ini -- I'm not entirely sure if this can be done more au
On Thu, May 05, 2016 at 11:01:48PM +0100, Ben Hutchings wrote:
>> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid
>> and
>> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and
>> updating
>> boot.ini -- I'm not entirely sure if this can be done more a
On Thu, 2016-05-05 at 23:29 +0200, Steinar H. Gunderson wrote:
> Package: linux-image-4.5.0-2-armmp-lpae
> Version: 4.5.2-1
> Severity: normal
>
> Hi,
>
> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid
> and
> installing 4.5.0-2-armmp-lpae (and generating the uInitrd
Package: linux-image-4.5.0-2-armmp-lpae
Version: 4.5.2-1
Severity: normal
Hi,
I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid and
installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating
boot.ini -- I'm not entirely sure if this can be done more a
18 matches
Mail list logo
