devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
	Linuxarm <linuxarm@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Xiaofei Tan <tanxiaofei@huawei.com>
Subject: Re: [PATCH v2 1/8] dt-bindings: scsi: hisi_sas: add an property of signal attenuation
Date: Fri, 2 Mar 2018 09:57:20 -0600	[thread overview]
Message-ID: <CAL_JsqJNxxyBDk_u=Wf2vGbgwa7act2NNc+zmxP7Ne80bFGqRA@mail.gmail.com> (raw)
In-Reply-To: <1520003182-26277-2-git-send-email-john.garry@huawei.com>

On Fri, Mar 2, 2018 at 9:06 AM, John Garry <john.garry@huawei.com> wrote:
> From: Xiaofei Tan <tanxiaofei@huawei.com>
>
> For some new boards with hip07 chipset we are required to
> set PHY config registers differently. The hw property which
> determines how to set these registers is in the PHY signal
> attenuation readings.
>
> This patch add an devicetree property, hisi-signal-attenuation,
> which is used to describe the signal attenuation of an board.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
>  Documentation/devicetree/bindings/scsi/hisilicon-sas.txt | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt b/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> index df3bef7..6f6876a 100644
> --- a/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> +++ b/Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> @@ -53,6 +53,13 @@ Main node required properties:
>  Optional main node properties:
>   - hip06-sas-v2-quirk-amt : when set, indicates that the v2 controller has the
>                             "am-max-transmissions" limitation.
> + - hisi-signal-attenuation : array of 3 32-bit values, containing de-emphasis,

The format for vendor prefixes is: <vendor prefix>,property-name

And should only be ones defined in vendor-prefixes.txt

> +               preshoot, and boost attenuation readings for the board. They
> +               are used to describe the signal attenuation of the board. These
> +               values' range is 7600 to 12400, and used to represent -24dB to
> +               24dB.
> +               The formula is "y = (x-10000)/10000". For example, 10478
> +               means 4.78dB.
>
>  Example:
>         sas0: sas@c1000000 {
> --
> 1.9.1
>

  reply	other threads:[~2018-03-02 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 15:06 [PATCH v2 0/8] hisi_sas: support x6000 board and some misc changes John Garry
2018-03-02 15:06 ` [PATCH v2 1/8] dt-bindings: scsi: hisi_sas: add an property of signal attenuation John Garry
2018-03-02 15:57   ` Rob Herring [this message]
2018-03-02 16:10     ` John Garry
2018-03-05 14:05       ` Rob Herring
2018-03-02 15:06 ` [PATCH v2 2/8] scsi: hisi_sas: support the property of signal attenuation for v2 hw John Garry
2018-03-02 15:06 ` [PATCH v2 3/8] scsi: hisi_sas: fix the issue of link rate inconsistency John Garry
2018-03-02 15:06 ` [PATCH v2 4/8] scsi: hisi_sas: fix the issue of setting linkrate register John Garry
2018-03-02 15:06 ` [PATCH v2 5/8] scsi: hisi_sas: increase timer expire of internal abort task John Garry
2018-03-02 15:06 ` [PATCH v2 6/8] scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req John Garry
2018-03-02 15:06 ` [PATCH v2 7/8] scsi: hisi_sas: fix return value of hisi_sas_task_prep() John Garry
2018-03-02 15:06 ` [PATCH v2 8/8] scsi: hisi_sas: Code cleanup and minor bug fixes John Garry

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='CAL_JsqJNxxyBDk_u=Wf2vGbgwa7act2NNc+zmxP7Ne80bFGqRA@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=tanxiaofei@huawei.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).