From: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
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, 3 Feb 2016 14:44:32 +0000 [thread overview]
Message-ID: <56B21250.5050807@imgtec.com> (raw)
In-Reply-To: <2782231.XGO9cUTm7n@wuerfel>
Hi,
On 03/02/16 13:47, Arnd Bergmann wrote:
> On Wednesday 03 February 2016 13:24:10 Zubair Lutfullah Kakakhel wrote:
>>> Typically we treat those special registers as part of the device itself
>>> and have a single device node for the AHCI controller and that one.
>>>
>>> What is your reason for doing it differently here?
>>
>> Two reasons
>>
>> 1- The hardware is like a proper split rather than additional hidden registers in
>> the same memory space.
>>
>> 2- Tons of devices in the field have the following DT node built in the bootloader.
>>
>> uctl@118006c000000 {
>> compatible = "cavium,octeon-7130-sata-uctl";
>> reg = <0x11800 0x6c000000 0x0 0x100>;
>> ...
>> sata: sata@16c0000000000 {
>> compatible = "cavium,octeon-7130-ahci";
>> reg = <0x16c00 0x00000000 0x0 0x200>;
>> ...
>> };
>> };
>>
>> The patch suggests a way to handle this.
>>
>
> Ok, fair enough. Also, you write in the binding that this is a bus
> bridge, so this indeed matches what the hardware does, and that's ok.
Thank-you.
>
> Does the bus bridge actually translate the entire 64-bit CPU MMIO space,
> or is it possible that it only handles one device (or a couple of
> them) with a fairly limited space?
This uctl is just for SATA devices.
>
> Maybe it's better to represent it as a #address-cells=<1> in the
> example, and have the child device appear at address 0 in there.
Possible in the example.
I'll update the example to
uctl@118006c000000 {
compatible = "cavium,octeon-7130-sata-uctl";
reg = <0x11800 0x6c000000 0x0 0x100>;
ranges; /* Direct mapping */
dma-ranges;
#address-cells = <1>;
#size-cells = <2>;
sata: sata@0 {
compatible = "cavium,octeon-7130-ahci";
reg = <0x16c00 0x00000000 0x0 0x200>;
interrupt-parent = <&cibsata>;
interrupts = <2 4>; /* Bit: 2, level */
};
};
>
> For the machines that already ship a DT, that would not matter though,
> it works either way.
>
> Arnd
>
WARNING: multiple messages have this Message-ID (diff)
From: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
To: Arnd Bergmann <arnd@arndb.de>
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, 3 Feb 2016 14:44:32 +0000 [thread overview]
Message-ID: <56B21250.5050807@imgtec.com> (raw)
In-Reply-To: <2782231.XGO9cUTm7n@wuerfel>
Hi,
On 03/02/16 13:47, Arnd Bergmann wrote:
> On Wednesday 03 February 2016 13:24:10 Zubair Lutfullah Kakakhel wrote:
>>> Typically we treat those special registers as part of the device itself
>>> and have a single device node for the AHCI controller and that one.
>>>
>>> What is your reason for doing it differently here?
>>
>> Two reasons
>>
>> 1- The hardware is like a proper split rather than additional hidden registers in
>> the same memory space.
>>
>> 2- Tons of devices in the field have the following DT node built in the bootloader.
>>
>> uctl@118006c000000 {
>> compatible = "cavium,octeon-7130-sata-uctl";
>> reg = <0x11800 0x6c000000 0x0 0x100>;
>> ...
>> sata: sata@16c0000000000 {
>> compatible = "cavium,octeon-7130-ahci";
>> reg = <0x16c00 0x00000000 0x0 0x200>;
>> ...
>> };
>> };
>>
>> The patch suggests a way to handle this.
>>
>
> Ok, fair enough. Also, you write in the binding that this is a bus
> bridge, so this indeed matches what the hardware does, and that's ok.
Thank-you.
>
> Does the bus bridge actually translate the entire 64-bit CPU MMIO space,
> or is it possible that it only handles one device (or a couple of
> them) with a fairly limited space?
This uctl is just for SATA devices.
>
> Maybe it's better to represent it as a #address-cells=<1> in the
> example, and have the child device appear at address 0 in there.
Possible in the example.
I'll update the example to
uctl@118006c000000 {
compatible = "cavium,octeon-7130-sata-uctl";
reg = <0x11800 0x6c000000 0x0 0x100>;
ranges; /* Direct mapping */
dma-ranges;
#address-cells = <1>;
#size-cells = <2>;
sata: sata@0 {
compatible = "cavium,octeon-7130-ahci";
reg = <0x16c00 0x00000000 0x0 0x200>;
interrupt-parent = <&cibsata>;
interrupts = <2 4>; /* Bit: 2, level */
};
};
>
> For the machines that already ship a DT, that would not matter though,
> it works either way.
>
> Arnd
>
next prev parent reply other threads:[~2016-02-03 14:44 UTC|newest]
Thread overview: 17+ 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:24 ` Zubair Lutfullah Kakakhel
2016-02-02 18:37 ` David Daney
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:24 ` Zubair Lutfullah Kakakhel
2016-02-03 13:41 ` Arnd Bergmann
2016-02-03 14:44 ` Zubair Lutfullah Kakakhel
2016-02-03 14:44 ` Zubair Lutfullah Kakakhel
2016-02-03 13:47 ` Arnd Bergmann
2016-02-03 14:44 ` Zubair Lutfullah Kakakhel [this message]
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:02 ` Zubair Lutfullah Kakakhel
2016-02-03 16:23 ` Arnd Bergmann
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=56B21250.5050807@imgtec.com \
--to=zubair.kakakhel@imgtec.com \
--cc=aleksey.makarov@caviumnetworks.com \
--cc=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.