devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Loc Ho <lho@apm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"olof@lixom.net" <olof@lixom.net>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"dmilburn@redhat.com" <dmilburn@redhat.com>,
	"jcm@redhat.com" <jcm@redhat.com>,
	"patches@apm.com" <patches@apm.com>, Tuan Phan <tphan@apm.com>,
	Suman Tripathi <stripathi@apm.com>
Subject: Re: [PATCH v9 2/4] Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding
Date: Wed, 15 Jan 2014 13:08:47 -0800	[thread overview]
Message-ID: <CAPw-ZTmVYfPLUVmtes3Gn8Z=+gyFtLoZxc-QUdHH7-ePjKAG9A@mail.gmail.com> (raw)
In-Reply-To: <5905127.tqJ3nFt5cj@wuerfel>

Hi,

>>
>> >> +- clocks             : Reference to the clock entry.
>> >> +- phys                       : PHY reference with parameter 0.
>> >
>> > The specific value of the phy-specifier shouldn't matter to this
>> > binding. What should matter is what it logically corresponds to.
>>
>> I not quite following this. Are you suggest that I drop the value 0.
>> In the binding, one needs to specify the mode of operation - 0 is for
>> SATA. Can you explain more?
>
> The SATA device should not care what the argument for the PHY
> device is. You could connect the same device to another PHY
> that has a different set of arguments, which is the whole point
> of abstracting it.
>

I understand what you wrote here. We should not have an argument from
the host controller. Then my question is how should the PHY node
indicates that it needs to be configured itself as an SATA PHY?

-Loc

  reply	other threads:[~2014-01-15 21:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  7:11 [PATCH v9 0/4] ata: Add APM X-Gene SoC SATA host controller support Loc Ho
2014-01-15  7:11 ` [PATCH v9 1/4] ata: Export required functions by APM X-Gene SATA driver Loc Ho
2014-01-15  7:11   ` [PATCH v9 2/4] Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding Loc Ho
2014-01-15  7:11     ` [PATCH v9 3/4] ata: Add APM X-Gene SoC SATA host controller driver Loc Ho
2014-01-15  7:11       ` [PATCH v9 4/4] arm64: Add APM X-Gene SoC SATA host controller DTS entries Loc Ho
2014-01-15 11:18     ` [PATCH v9 2/4] Documentation: Add documentation for APM X-Gene SoC SATA host controller DTS binding Mark Rutland
2014-01-15 20:04       ` Loc Ho
2014-01-15 20:10         ` Arnd Bergmann
2014-01-15 21:08           ` Loc Ho [this message]
2014-01-15 21:12             ` Arnd Bergmann
2014-01-15 22:07               ` Loc Ho
2014-01-15 23:59                 ` Loc Ho
2014-01-16 10:38                   ` 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='CAPw-ZTmVYfPLUVmtes3Gn8Z=+gyFtLoZxc-QUdHH7-ePjKAG9A@mail.gmail.com' \
    --to=lho@apm.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmilburn@redhat.com \
    --cc=jcm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=patches@apm.com \
    --cc=stripathi@apm.com \
    --cc=tj@kernel.org \
    --cc=tphan@apm.com \
    /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).