Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752103AbaGaPcB (ORCPT ); Thu, 31 Jul 2014 11:32:01 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:55445 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750883AbaGaPb7 (ORCPT ); Thu, 31 Jul 2014 11:31:59 -0400 Message-ID: <53DA6171.30100@wwwdotorg.org> Date: Thu, 31 Jul 2014 09:32:01 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Mikko Perttunen CC: Andrew Bresticker , Peter De Schrijver , Prashant Gaikwad , Mike Turquette , Thierry Reding , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-tegra@vger.kernel.org" Subject: Re: [PATCH 5/8] of: Add Tegra124 EMC bindings References: <1405088313-20048-1-git-send-email-mperttunen@nvidia.com> <1405088313-20048-6-git-send-email-mperttunen@nvidia.com> <53CD860B.7030800@wwwdotorg.org> <53CE9514.1050903@wwwdotorg.org> <53CEA093.6060106@wwwdotorg.org> <53D75B90.7050501@nvidia.com> <53D7C276.2080204@wwwdotorg.org> <53DA1EF0.7060207@nvidia.com> <53DA230E.7060903@nvidia.com> In-Reply-To: <53DA230E.7060903@nvidia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/31/2014 05:05 AM, Mikko Perttunen wrote: > On 31/07/14 13:48, Mikko Perttunen wrote: >>> >>> I see that the TRM implies the whole 4-bit field is RAM code, rather >>> than there being 2 separate 2-bit fields for RAM code and boot device >>> code. Can you please file a bug against the TRM to document this >>> correctly? (The details of which bits are which are visible on the >>> Jetson TK1 schematics for example). >> >> Yes, I'll file a bug. > > On a closer look, the downstream kernel has been recently updated to > consider the whole 4 bits the ram code. The relevant bug also has a > comment mentioning that starting from T124, the whole 4 bits is > considered the RAM code. That's odd. Given the structure of the BCT hasn't change, I suspect that's a documentation bug that's propagated elsewhere. Can you send me the bug number internally, and I'll take a look? Thanks. -- 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/