SUPERH platform development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 8/8] ARM: shmobile: henninger: Add dummy PCIe bus clock
Date: Thu, 12 Jun 2014 16:47:59 +0000	[thread overview]
Message-ID: <5399D9BF.6030208@cogentembedded.com> (raw)
In-Reply-To: <1401261843-6964-9-git-send-email-phil.edworthy@renesas.com>

Hello.

On 06/12/2014 07:41 PM, Phil Edworthy wrote:

>>>> Since the CPU's dtsi refers to pcie_bus_clock, we need an entry in
>>>> the board's dts, even if we aren't using PCIe.

>>>      I don't quite understand that last part: there's PCIe slot in the
>>> Henninger's schematics (although it doesn't seem to be soldered in the
>>> early board version).

>>      In fact, we're in process of verifying PCIe on Henninger (soldered the
>> connector); at least the configuration space accesses work OK...

> Do you mean the internal Root-Complex config accesses work ok, or card ones?

    We inserted an Intel Wi-Fi card and saw PCI-PCI bridge and network 
controller in lspci's output. Another (Ethernet) card didn't work though...

> One thing we noticed on the Koelsch board is that some cards need Aux 3.3V to be supplied before they will work. By default on the Koelsch board, this is not supplied - you have to add link R719.

    Thanks for the info.

> Regards
> Phil

WBR, Sergei


  parent reply	other threads:[~2014-06-12 16:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28  7:24 [PATCH 8/8] ARM: shmobile: henninger: Add dummy PCIe bus clock Phil Edworthy
2014-06-11 21:03 ` Sergei Shtylyov
2014-06-11 23:24 ` Sergei Shtylyov
2014-06-12  8:36 ` Phil Edworthy
2014-06-12 15:41 ` Phil Edworthy
2014-06-12 16:42 ` Sergei Shtylyov
2014-06-12 16:47 ` Sergei Shtylyov [this message]
2014-06-16 22:55 ` Sergei Shtylyov
2014-06-17  7:41 ` Phil Edworthy
2014-06-19 22:02 ` Sergei Shtylyov
2014-06-23  9:19 ` Phil Edworthy
2014-06-24 21:46 ` Sergei Shtylyov
2014-06-25  9:43 ` Phil Edworthy

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=5399D9BF.6030208@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --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