From: Arnd Bergmann <arnd@arndb.de>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: dgilbert@interlog.com, Loc Ho <lho@apm.com>,
olof@lixom.net, tj@kernel.org, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jcm@redhat.com,
patches@apm.com, Tuan Phan <tphan@apm.com>,
Suman Tripathi <stripathi@apm.com>
Subject: Re: [PATCH v4 2/4] Documentation: Add APM X-Gene SoC 15Gbps Multi-purpose PHY driver binding documentation
Date: Thu, 12 Dec 2013 22:09:22 +0100 [thread overview]
Message-ID: <201312122209.22742.arnd@arndb.de> (raw)
In-Reply-To: <1386867353.5985.7.camel@dabdike>
On Thursday 12 December 2013, James Bottomley wrote:
> > > I'm completely confused by this description. Can you rephrase this?
> > > It sounds like the only possible values are <1 3 7> for this property.
> >
> > Most likely Gen1, Gen2 and Gen3 are SATA-speak corresponding to SAS's
> > G1, G2 and G3:
> >
> > G1 Gen1 1.5 Gbps
> > G2 Gen2 3 Gbps
> > G3 Gen3 6 Gbps
> > G4 - 12 Gbps
> > G5 - 24 Gbps
>
> Electrically, SAS phys and SATA phys are identical. We already have a
> SAS phy abstraction in libsas ... when looking at a separable phy
> implementation, shouldn't we be doing something that works for both
> instead of just SATA?
This PHY is also used for ethernet and for PCIe, even though the driver
handles only the SATA case so far. Can the SAS abstraction deal with this?
How do you describe a SAS PHY in DT?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] Documentation: Add APM X-Gene SoC 15Gbps Multi-purpose PHY driver binding documentation
Date: Thu, 12 Dec 2013 22:09:22 +0100 [thread overview]
Message-ID: <201312122209.22742.arnd@arndb.de> (raw)
In-Reply-To: <1386867353.5985.7.camel@dabdike>
On Thursday 12 December 2013, James Bottomley wrote:
> > > I'm completely confused by this description. Can you rephrase this?
> > > It sounds like the only possible values are <1 3 7> for this property.
> >
> > Most likely Gen1, Gen2 and Gen3 are SATA-speak corresponding to SAS's
> > G1, G2 and G3:
> >
> > G1 Gen1 1.5 Gbps
> > G2 Gen2 3 Gbps
> > G3 Gen3 6 Gbps
> > G4 - 12 Gbps
> > G5 - 24 Gbps
>
> Electrically, SAS phys and SATA phys are identical. We already have a
> SAS phy abstraction in libsas ... when looking at a separable phy
> implementation, shouldn't we be doing something that works for both
> instead of just SATA?
This PHY is also used for ethernet and for PCIe, even though the driver
handles only the SATA case so far. Can the SAS abstraction deal with this?
How do you describe a SAS PHY in DT?
Arnd
next prev parent reply other threads:[~2013-12-12 21:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 7:30 (unknown), Loc Ho
2013-12-12 7:30 ` No subject Loc Ho
2013-12-12 7:30 ` [PATCH v4 1/4] PHY: Add function set_speed to generic PHY framework Loc Ho
2013-12-12 7:30 ` Loc Ho
2013-12-12 7:30 ` [PATCH v4 2/4] Documentation: Add APM X-Gene SoC 15Gbps Multi-purpose PHY driver binding documentation Loc Ho
2013-12-12 7:30 ` Loc Ho
2013-12-12 7:30 ` [PATCH v4 3/4] PHY: add APM X-Gene SoC 15Gbps Multi-purpose PHY driver Loc Ho
2013-12-12 7:30 ` Loc Ho
2013-12-12 7:30 ` [PATCH v4 4/4] arm64: Add APM X-Gene SoC 15Gbps Multi-purpose PHY DTS entries Loc Ho
2013-12-12 7:30 ` Loc Ho
2013-12-12 13:27 ` [PATCH v4 2/4] Documentation: Add APM X-Gene SoC 15Gbps Multi-purpose PHY driver binding documentation Arnd Bergmann
2013-12-12 13:27 ` Arnd Bergmann
2013-12-12 14:31 ` Douglas Gilbert
2013-12-12 14:31 ` Douglas Gilbert
2013-12-12 16:55 ` James Bottomley
2013-12-12 16:55 ` James Bottomley
2013-12-12 21:09 ` Arnd Bergmann [this message]
2013-12-12 21:09 ` Arnd Bergmann
2013-12-12 20:29 ` Arnd Bergmann
2013-12-12 20:29 ` Arnd Bergmann
2013-12-12 23:30 ` Loc Ho
2013-12-12 23:30 ` Loc Ho
2013-12-12 16:43 ` Loc Ho
2013-12-12 16:43 ` Loc Ho
2013-12-12 21:25 ` Arnd Bergmann
2013-12-12 21:25 ` Arnd Bergmann
2013-12-12 23:46 ` Loc Ho
2013-12-12 23:46 ` Loc Ho
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=201312122209.22742.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=devicetree@vger.kernel.org \
--cc=dgilbert@interlog.com \
--cc=jcm@redhat.com \
--cc=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 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.