From: Arnd Bergmann <arnd@arndb.de>
To: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Cc: tj@kernel.org, hdegoede@redhat.com, david.daney@cavium.com,
aleksey.makarov@caviumnetworks.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH v6] SATA: OCTEON: support SATA on OCTEON platform
Date: Wed, 03 Feb 2016 17:23:18 +0100 [thread overview]
Message-ID: <8562433.7oWe1ikqcL@wuerfel> (raw)
In-Reply-To: <56B2247D.5040501@imgtec.com>
On Wednesday 03 February 2016 16:02:05 Zubair Lutfullah Kakakhel wrote:
> Hence, I find the original binding simpler and easier to understand when looking at the hardware manual
>
> + uctl@118006c000000 {
> + compatible = "cavium,octeon-7130-sata-uctl";
> + reg = <0x11800 0x6c000000 0x0 0x100>;
> + ranges; /* Direct mapping */
> + dma-ranges;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + sata: sata@16c0000000000 {
> + compatible = "cavium,octeon-7130-ahci";
> + reg = <0x16c00 0x00000000 0x0 0x200>;
> + interrupt-parent = <&cibsata>;
> + interrupts = <2 4>; /* Bit: 2, level */
> + };
> + };
>
> Is it possible to let this example go in as is?
>
I don't have the hardware manual, so I'm just guessing what the hardware
looks like. If the manual describes the device as a bridge with a 1:1 mapping,
then your existing example above absolutely makes sense.
Arnd
prev parent reply other threads:[~2016-02-03 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 18:24 [PATCH v6] SATA: OCTEON: support SATA on OCTEON platform Zubair Lutfullah Kakakhel
2016-02-02 18:37 ` David Daney
2016-02-02 20:48 ` Arnd Bergmann
2016-02-03 13:24 ` Zubair Lutfullah Kakakhel
2016-02-03 13:41 ` Arnd Bergmann
2016-02-03 14:44 ` Zubair Lutfullah Kakakhel
2016-02-03 13:47 ` Arnd Bergmann
2016-02-03 14:44 ` Zubair Lutfullah Kakakhel
2016-02-03 15:31 ` Arnd Bergmann
2016-02-03 16:02 ` Zubair Lutfullah Kakakhel
2016-02-03 16:23 ` Arnd Bergmann [this message]
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=8562433.7oWe1ikqcL@wuerfel \
--to=arnd@arndb.de \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=aleksey.makarov@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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