From: Rob Herring <robh@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 3/3] dt-bindings: Change the meaning of clock-frequency
Date: Mon, 19 Oct 2020 16:22:32 -0500 [thread overview]
Message-ID: <20201019212232.GA3619458@bogus> (raw)
In-Reply-To: <20201016062602.20014-4-billy_tsai@aspeedtech.com>
On Fri, Oct 16, 2020 at 02:26:02PM +0800, Billy Tsai wrote:
> Integration of the usage of msg-timing and addr-timing to clock-frequency.
> User can just set it to adjust the peci work efficient.
You're breaking the ABI changing this.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> .../devicetree/bindings/peci/peci-aspeed.yaml | 56 +++++++++----------
> 1 file changed, 28 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> index 0f5c2993fe9b..7c6c895784af 100644
> --- a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> +++ b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> @@ -40,31 +40,33 @@ properties:
> maxItems: 1
>
> clock-frequency:
> - # Operation frequency of PECI controller in units of Hz.
> - minimum: 187500
> - maximum: 24000000
> -
> - msg-timing:
> - description: |
> - Message timing negotiation period. This value will determine the period
> - of message timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> -
> - addr-timing:
> - description: |
> - Address timing negotiation period. This value will determine the period
> - of address timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> + # The bit frequency of PECI negotiation stage in units of Hz.
> + # Driver will calculate the best divisor setting of msg-timing and
> + # addr-timing to meet the value.
Use 'description' rather than comments.
> + minimum: 2000
> + maximum: 2000000
> +
> + # msg-timing:
> + # description: |
> + # Message timing negotiation period. This value will determine the period
> + # of message timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
Why is this commented out?
> +
> + # addr-timing:
> + # description: |
> + # Address timing negotiation period. This value will determine the period
> + # of address timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
>
> rd-sampling-point:
> description: |
> @@ -114,9 +116,7 @@ examples:
> interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&syscon ASPEED_CLK_GATE_REF0CLK>;
> resets = <&syscon ASPEED_RESET_PECI>;
> - clock-frequency = <24000000>;
> - msg-timing = <1>;
> - addr-timing = <1>;
> + clock-frequency = <2000000>;
> rd-sampling-point = <8>;
> cmd-timeout-ms = <1000>;
> };
> --
> 2.17.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Billy Tsai <billy_tsai@aspeedtech.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
jae.hyun.yoo@linux.intel.com, linux-aspeed@lists.ozlabs.org,
BMC-SW@aspeedtech.com, andrew@aj.id.au,
vernon.mauery@linux.intel.com, joel@jms.id.au,
haiyue.wang@linux.intel.com, james.feist@linux.intel.com
Subject: Re: [PATCH 3/3] dt-bindings: Change the meaning of clock-frequency
Date: Mon, 19 Oct 2020 16:22:32 -0500 [thread overview]
Message-ID: <20201019212232.GA3619458@bogus> (raw)
In-Reply-To: <20201016062602.20014-4-billy_tsai@aspeedtech.com>
On Fri, Oct 16, 2020 at 02:26:02PM +0800, Billy Tsai wrote:
> Integration of the usage of msg-timing and addr-timing to clock-frequency.
> User can just set it to adjust the peci work efficient.
You're breaking the ABI changing this.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> .../devicetree/bindings/peci/peci-aspeed.yaml | 56 +++++++++----------
> 1 file changed, 28 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> index 0f5c2993fe9b..7c6c895784af 100644
> --- a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> +++ b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> @@ -40,31 +40,33 @@ properties:
> maxItems: 1
>
> clock-frequency:
> - # Operation frequency of PECI controller in units of Hz.
> - minimum: 187500
> - maximum: 24000000
> -
> - msg-timing:
> - description: |
> - Message timing negotiation period. This value will determine the period
> - of message timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> -
> - addr-timing:
> - description: |
> - Address timing negotiation period. This value will determine the period
> - of address timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> + # The bit frequency of PECI negotiation stage in units of Hz.
> + # Driver will calculate the best divisor setting of msg-timing and
> + # addr-timing to meet the value.
Use 'description' rather than comments.
> + minimum: 2000
> + maximum: 2000000
> +
> + # msg-timing:
> + # description: |
> + # Message timing negotiation period. This value will determine the period
> + # of message timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
Why is this commented out?
> +
> + # addr-timing:
> + # description: |
> + # Address timing negotiation period. This value will determine the period
> + # of address timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
>
> rd-sampling-point:
> description: |
> @@ -114,9 +116,7 @@ examples:
> interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&syscon ASPEED_CLK_GATE_REF0CLK>;
> resets = <&syscon ASPEED_RESET_PECI>;
> - clock-frequency = <24000000>;
> - msg-timing = <1>;
> - addr-timing = <1>;
> + clock-frequency = <2000000>;
> rd-sampling-point = <8>;
> cmd-timeout-ms = <1000>;
> };
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Billy Tsai <billy_tsai@aspeedtech.com>
Cc: joel@jms.id.au, andrew@aj.id.au, jae.hyun.yoo@linux.intel.com,
haiyue.wang@linux.intel.com, james.feist@linux.intel.com,
vernon.mauery@linux.intel.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, BMC-SW@aspeedtech.com
Subject: Re: [PATCH 3/3] dt-bindings: Change the meaning of clock-frequency
Date: Mon, 19 Oct 2020 16:22:32 -0500 [thread overview]
Message-ID: <20201019212232.GA3619458@bogus> (raw)
In-Reply-To: <20201016062602.20014-4-billy_tsai@aspeedtech.com>
On Fri, Oct 16, 2020 at 02:26:02PM +0800, Billy Tsai wrote:
> Integration of the usage of msg-timing and addr-timing to clock-frequency.
> User can just set it to adjust the peci work efficient.
You're breaking the ABI changing this.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> .../devicetree/bindings/peci/peci-aspeed.yaml | 56 +++++++++----------
> 1 file changed, 28 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> index 0f5c2993fe9b..7c6c895784af 100644
> --- a/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> +++ b/Documentation/devicetree/bindings/peci/peci-aspeed.yaml
> @@ -40,31 +40,33 @@ properties:
> maxItems: 1
>
> clock-frequency:
> - # Operation frequency of PECI controller in units of Hz.
> - minimum: 187500
> - maximum: 24000000
> -
> - msg-timing:
> - description: |
> - Message timing negotiation period. This value will determine the period
> - of message timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> -
> - addr-timing:
> - description: |
> - Address timing negotiation period. This value will determine the period
> - of address timing negotiation to be issued by PECI controller. The unit
> - of the programmed value is four times of PECI clock period.
> - allOf:
> - - $ref: /schemas/types.yaml#/definitions/uint32
> - - minimum: 0
> - maximum: 255
> - default: 1
> + # The bit frequency of PECI negotiation stage in units of Hz.
> + # Driver will calculate the best divisor setting of msg-timing and
> + # addr-timing to meet the value.
Use 'description' rather than comments.
> + minimum: 2000
> + maximum: 2000000
> +
> + # msg-timing:
> + # description: |
> + # Message timing negotiation period. This value will determine the period
> + # of message timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
Why is this commented out?
> +
> + # addr-timing:
> + # description: |
> + # Address timing negotiation period. This value will determine the period
> + # of address timing negotiation to be issued by PECI controller. The unit
> + # of the programmed value is four times of PECI clock period.
> + # allOf:
> + # - $ref: /schemas/types.yaml#/definitions/uint32
> + # - minimum: 0
> + # maximum: 255
> + # default: 1
>
> rd-sampling-point:
> description: |
> @@ -114,9 +116,7 @@ examples:
> interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&syscon ASPEED_CLK_GATE_REF0CLK>;
> resets = <&syscon ASPEED_RESET_PECI>;
> - clock-frequency = <24000000>;
> - msg-timing = <1>;
> - addr-timing = <1>;
> + clock-frequency = <2000000>;
> rd-sampling-point = <8>;
> cmd-timeout-ms = <1000>;
> };
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-10-19 21:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 6:25 [PATCH 0/3] Extend peci feature Billy Tsai
2020-10-16 6:25 ` Billy Tsai
2020-10-16 6:25 ` Billy Tsai
2020-10-16 6:26 ` [PATCH 1/3] peci: aspeed: make the driver support 64byte mode Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-16 6:26 ` [PATCH 2/3] peci: aspeed: Auto calculate the adapter divisor Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-28 4:40 ` Joel Stanley
2020-10-28 4:40 ` Joel Stanley
2020-10-28 4:40 ` Joel Stanley
2020-10-16 6:26 ` [PATCH 3/3] dt-bindings: Change the meaning of clock-frequency Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-16 6:26 ` Billy Tsai
2020-10-19 21:22 ` Rob Herring [this message]
2020-10-19 21:22 ` Rob Herring
2020-10-19 21:22 ` Rob Herring
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=20201019212232.GA3619458@bogus \
--to=robh@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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.