devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Alan Tull <atull@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: stratix10: i2c clock running out of spec
Date: Wed, 15 Aug 2018 10:08:24 -0500	[thread overview]
Message-ID: <dd109cc6-00a8-244b-07e9-97e29739d804@kernel.org> (raw)
In-Reply-To: <20180808154241.3760-1-atull@kernel.org>



On 08/08/2018 10:42 AM, Alan Tull wrote:
> DesignWare I2C controller was observed running at 105.93kHz rather
> than the specified 100kHz.  Adjust device tree settings to bring it
> within spec (a slightly conservative 98 MHz).
> 
> Signed-off-by: Alan Tull <atull@kernel.org>
> ---
>  arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> index 6edc4fa..53cf195 100644
> --- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> +++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> @@ -124,6 +124,8 @@
>  &i2c1 {
>  	status = "okay";
>  	clock-frequency = <100000>;
> +	i2c-sda-falling-time-ns = <890>;  /* hcnt */
> +	i2c-sdl-falling-time-ns = <890>;  /* lcnt */
>  
>  	adc@14 {
>  		compatible = "lltc,ltc2497";
> 

Applied!

Thanks,
Dinh

      reply	other threads:[~2018-08-15 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 15:42 [PATCH] arm64: dts: stratix10: i2c clock running out of spec Alan Tull
2018-08-15 15:08 ` Dinh Nguyen [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=dd109cc6-00a8-244b-07e9-97e29739d804@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=atull@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.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).