public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: cory.tusar@pid1solutions•com (Cory Tusar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: dts: vf610-zii-dev: Add ZII development board.
Date: Thu, 25 Feb 2016 11:24:43 -0500	[thread overview]
Message-ID: <56CF2ACB.7080301@pid1solutions.com> (raw)
In-Reply-To: <c67c93683d9440bd050386df0e200881@agner.ch>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/23/2016 02:36 PM, Stefan Agner wrote:
> Hi Andrew,
> 
> Some comments below:
> 
> On 2016-02-21 11:51, Andrew Lunn wrote:
>> From: Cory Tusar <cory.tusar@pid1solutions•com>
>>
>> This commit adds support for Rev. B of a Zodiac Inflight Innovations
>> development board, mainly intended for DSA and ARINC 429 development
>> work.
>>
>> Signed-off-by: Cory Tusar <cory.tusar@pid1solutions•com>
>> Signed-off-by: Andrew Lunn <andrew@lunn•ch>

[snip]

>> +&L2 {
>> +	arm,data-latency = <2 1 2>;
>> +	arm,tag-latency = <3 2 3>;
>> +};
> 
> Are you sure about that?
> 
> With 9c17190595 ("ARM: dts: vf610: use reset values for L2 cache
> latencies") we have reasonable values in the base device tree
> vf610.dtsi, I think therefor this is not necessary anymore, even if you
> use 500MHz as CPU clock.

Hi Stefan,

We'd had some pretty serious instability on our platform with the older
values (prior to the commit mentioned above).  I recall seeing that
change go in, and reviewed the discussion on Freescale's support forum,
but left things as they were pending official comment from Freescale.

"If it isn't broken...."

We can certainly try the new defaults and see if it crops up again.

FWIW, yes, we're running at 500 MHz.

Best regards,
- -Cory


- -- 
Cory Tusar
Principal
PID 1 Solutions, Inc.


"There are two ways of constructing a software design.  One way is to
 make it so simple that there are obviously no deficiencies, and the
 other way is to make it so complicated that there are no obvious
 deficiencies."  --Sir Charles Anthony Richard Hoare

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbPKssACgkQHT1tsfGwHJ8acwCbB0/2AZrfGzRlIrr01igdDbGH
Q7QAoKtZcm0eyQNQxO3IlZUA6dSY+GEf
=sdAe
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2016-02-25 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 19:51 [PATCH] ARM: dts: vf610-zii-dev: Add ZII development board Andrew Lunn
2016-02-23 19:36 ` Stefan Agner
2016-02-23 20:32   ` Andrew Lunn
2016-02-25 16:24   ` Cory Tusar [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=56CF2ACB.7080301@pid1solutions.com \
    --to=cory.tusar@pid1solutions$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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