Date: Thu, 15 Nov 2012 08:11:01 +0100
From: Thierry Reding <thierry.reding@avionic-design.de>
To: Terje =?utf-8?Q?Bergstr=C3=B6m?= <tbergstrom@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
        "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: Add Tegra20 host1x support
Message-ID: <20121115071101.GA15528@avionic-0098.mockup.avionic-design.de>
References: <1352467202-27903-1-git-send-email-thierry.reding@avionic-design.de>
 <1352467202-27903-2-git-send-email-thierry.reding@avionic-design.de>
 <50A357D3.9080002@nvidia.com>
 <20121114084931.GA31837@avionic-0098.mockup.avionic-design.de>
 <50A3712E.7000104@nvidia.com>
 <20121114105406.GA31455@avionic-0098.mockup.avionic-design.de>
 <50A3C485.7080704@wwwdotorg.org>
 <20121114200415.GA10335@avionic-0098.mockup.avionic-design.de>
 <50A49211.4060303@nvidia.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5"
Content-Disposition: inline
In-Reply-To: <50A49211.4060303@nvidia.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2685
Lines: 66


--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 15, 2012 at 08:56:17AM +0200, Terje Bergstr=C3=B6m wrote:
> On 14.11.2012 22:04, Thierry Reding wrote:
> > According to tegra20_clocks_data.c, the maximum clock frequency for
> > host1x is 166 MHz, so 216 is probably not a good idea. 150 MHz sounds
> > sensible, though.
> >=20
> > I was going to send a new version of the patch set tonight, but I'll
> > wait until I can test it tomorrow and once Terje has reported back that
> > things work fine.
>=20
> Hi,
>=20
> I tried with 150MHz, 133.3MHz, 100MHz and as an act of desperation
> 300MHz. None of them worked. pll_p with 216MHz seems to be the only
> option that works on my board.
>=20
> But, as said, this seems to affect only the case where nvhost is
> integrated, too, so your patch creates a working DRM and frame buffer,
> so I'm fine with leaving it as it was in the original patch set.

I just tried with 150 MHz as well and it seems to work properly. So as
Stephen pointed out, 144 MHz is not a supported frequency for host1x,
and therefore I'll just leave the valid (and working) 150 MHz in.

> Meanwhile, we need to figure out if we somehow misprogram PLLC or host1x
> clock when it's attached to PLLC on Tegra20.

Yes, absolutely. Among other things there's still the upcoming and much
needed rework of the PLL frequency table code, so while at that we could
look at the issue you're seeing as well.

Thierry

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBAgAGBQJQpJWFAAoJEN0jrNd/PrOhMYcP/1058PAw6WMUj7Jy/pk/HT4G
x3qF9hdxJGvEzPplLIlDWKWL1CVSV0U7a9nIbjJj44puaWsievLTxGLfzuq7qDkf
uaoN3GI6JRwZjunFUPJnBzJaaTNl8tgWRCqgyEunVLsz9tPUrRuReyWkq1hp5xSt
Cwnqc+DBSO/IXzJuPYBmRGWCBkNBwZ9gh1iSVGaSK1uswU3LPic2ZYYYtxFlBfUi
cJlTlWcOzPsXgqI1NXEH51L0EP3Z7RwZ4ZBZDN8SFgjjITz+AlMNucu0fPV9XkVq
9y7MBXcagjFBL4buyyv71G5NETHv7DhDv3fazYTcjeCWyF63XwJLDkZwDZPgyOrv
gZMRDhf2NJQbJNfbL2R0YTQNgcDYUwG1hUGSfSIZ/A+hxwV1O6yt3jzabR2bh0HE
FVQG5kWVnA9xP0DEcM8fLXVVO4U/i6sl8QPQH/3Wk7UcOKm5hzNMbGNSz047nO5p
b9A5jam7qSkQlbQTxqPBT9P8ZgXLe47xu8MfYiy/AWk6cctIjfTqiyiNLudW/s1g
Nr8WsSjS51S5y5hLV9yDHxXyzI0ifn01plmGsBByE4LD89GMbJftT6lPhdc8IVMm
yn6lwj4MSkTorrtXEIPSYRNu8jYW43fpU07X9lvcybD4Xw4GzvEvuREVBWUW8FBE
BkCn+8pEKNoriy6x4ULU
=PYDF
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/