linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dashie@sigpipe.me (Dashie)
To: linux-arm-kernel@lists.infradead.org
Subject: Stuck getting DTS working for a new kirkwood board
Date: Sat, 22 Feb 2014 20:00:04 +0100	[thread overview]
Message-ID: <5308F3B4.6010409@sigpipe.me> (raw)
In-Reply-To: <20140221200855.GM7862@titan.lakedaemon.net>

Hi,

On 02/21/2014 09:08 PM, Jason Cooper wrote:
>> Well, with kirkwood_defconfig it doesn't find the SATA PHY and panic.
>> So i've used my debian config, make oldconfig, built and ... the toy is
>> booting.
> Yes, this is a known issue.  You worked around it by enabling generic
> phy support (it's most likely in the other configs).
Well, i've done some more tests and found that i've commented the
sata at 80000 {} part of the DTS, but does not remember if that was after
trying "debian config".

If i uncomment it, i got the kernel panic with "sata_mv f1080000.sata:
unable to find phy".

About generic phy, is it CONFIG_GENERIC_PHY ? I't already to =y in my
.config actually.
I have CONFIG_PHY_MVEBU_SATA=y and CONFIG_SATA_MV=y too.

Dashie.

  parent reply	other threads:[~2014-02-22 19:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 21:22 Stuck getting DTS working for a new kirkwood board Dashie
2014-02-21  1:34 ` Jason Cooper
2014-02-21  7:39   ` Dashie
2014-02-21 15:15     ` Jason Cooper
2014-02-21 19:21       ` Dashie
2014-02-21 20:08         ` Jason Cooper
2014-02-21 22:01           ` Dashie
2014-02-21 22:12             ` Andrew Lunn
2014-02-22  8:54               ` Dashie
2014-02-22 18:41                 ` Andrew Lunn
2014-02-22 18:50                   ` Dashie
2014-02-22 19:30                     ` Andrew Lunn
2014-02-22 19:44                       ` Dashie
2014-02-22 22:25                         ` Sebastian Hesselbarth
2014-02-22 18:44                 ` Gerhard Sittig
2014-02-22 19:00           ` Dashie [this message]
2014-02-22 19:30             ` Jason Cooper
2014-03-26  1:01               ` Jason Cooper

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=5308F3B4.6010409@sigpipe.me \
    --to=dashie@sigpipe.me \
    --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).