openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: Matthew Barth <msbarth@linux.ibm.com>,
	openbmc@lists.ozlabs.org, joel@jms.id.au
Subject: Re: [PATCH linux dev-5.8] ARM: dts: aspeed: rainier-4u: Update fan config
Date: Tue, 24 Nov 2020 13:32:39 -0600	[thread overview]
Message-ID: <4d404ce62d93da96183dc13a7dd908767b13c83c.camel@linux.ibm.com> (raw)
In-Reply-To: <20201124045512.2008095-1-msbarth@linux.ibm.com>

On Mon, 2020-11-23 at 22:55 -0600, Matthew Barth wrote:
> Rainier 4U systems has single rotor fans with a tach pulse of 4.
> 

Reviewed-by: Eddie James <eajames@linux.ibm.com>

> Signed-off-by: Matthew Barth <msbarth@linux.ibm.com>
> ---
>  arch/arm/boot/dts/aspeed-bmc-ibm-rainier-4u.dts | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier-4u.dts
> b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier-4u.dts
> index 291f7d6c9979..f7fd3b3c90d0 100644
> --- a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier-4u.dts
> +++ b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier-4u.dts
> @@ -22,16 +22,30 @@ power-supply@6b {
> 
>  &fan0 {
>  	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
>  };
> 
>  &fan1 {
>  	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
>  };
> 
>  &fan2 {
>  	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
>  };
> 
>  &fan3 {
>  	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
> +};
> +
> +&fan4 {
> +	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
> +};
> +
> +&fan5 {
> +	tach-pulses = <4>;
> +	/delete-property/ maxim,fan-dual-tach;
>  };


      reply	other threads:[~2020-11-24 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  4:55 [PATCH linux dev-5.8] ARM: dts: aspeed: rainier-4u: Update fan config Matthew Barth
2020-11-24 19:32 ` Eddie James [this message]

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=4d404ce62d93da96183dc13a7dd908767b13c83c.camel@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=msbarth@linux.ibm.com \
    --cc=openbmc@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 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).