Thread (19 messages) 19 messages, 4 authors, 2012-11-08

RE: [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX

flat view
STALE5097d

From: N, Mugunthan V <hidden>
Date: 2012-11-02 10:42:04
Also in: linux-arm-kernel, linux-omap

-----Original Message-----
From: Richard Cochran [mailto:richardcochran@gmail.com]
Sent: Friday, November 02, 2012 2:26 PM
To: N, Mugunthan V
Cc: Cousson, Benoit; Hiremath, Vaibhav; netdev@vger.kernel.org;
paul@pwsan.com; linux-arm-kernel@lists.infradead.org; linux-
omap@vger.kernel.org
Subject: Re: [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module
nodes for AM33XX

On Fri, Nov 02, 2012 at 08:46:46AM +0000, N, Mugunthan V wrote:
quoted
quoted
Do you expect to have several instance of the same IP with
different
quoted
quoted
parameters here?
Though CPSW is a single IP in AM335X, CPSW has sub modules like
CPDMA, ALE,
quoted
SLIVER, CPTS and SLAVES where is IP integrator can locate it at
different
quoted
offsets. For example comparing the CPSW ip in TI814X and AM335X all
the
quoted
above offsets are changed. So I have kept all these offsets in DT as
driver
quoted
should not hold any SoC related informations
Did you see the two messages on this point from yesterday?
I saw those posts. The CPSW ip version changes tracks the internal IP
changes and there is no possible way to track the offset changes. For
example CPTS sub module offsets in DM814x and AM335x are different
though the CPTS version is same in both IP versions. So keeping these
offset in DT will make the same driver works directly with DT changes
for future SoC.

Regards
Mugunthan V N
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help