All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Vaibhav Hiremath <hvaibhav@ti.com>, <netdev@vger.kernel.org>,
	<paul@pwsan.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-omap@vger.kernel.org>, Mugunthan V N <mugunthanvnm@ti.com>
Subject: Re: [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX
Date: Thu, 1 Nov 2012 10:28:47 +0100	[thread overview]
Message-ID: <509240CF.6060909@ti.com> (raw)
In-Reply-To: <20121101074508.GA2637@netboy.at.omicron.at>

On 11/1/2012 8:45 AM, Richard Cochran wrote:
> On Wed, Oct 31, 2012 at 04:17:27PM +0100, Benoit Cousson wrote:
>>> +			compatible = "ti,cpsw";
>>> +			ti,hwmods = "cpgmac0";
>>> +			cpdma_channels = <8>;
>>> +			host_port_no = <0>;
>>> +			cpdma_reg_ofs = <0x800>;
>>> +			cpdma_sram_ofs = <0xa00>;
>>> +			ale_reg_ofs = <0xd00>;
>>> +			ale_entries = <1024>;
>>> +			host_port_reg_ofs = <0x108>;
>>> +			hw_stats_reg_ofs = <0x900>;
>>> +			bd_ram_ofs = <0x2000>;
>>> +			bd_ram_size = <0x2000>;
>>> +			no_bd_ram = <0>;
>>> +			rx_descs = <64>;
>>> +			mac_control = <0x20>;
>>
>> Do you have to store all these data in the DTS? Cannot it be in the driver?
>>
>> Do you expect to have several instance of the same IP with different
>> parameters here?
>
> As I understand it, there are only two different layouts for the CPSW,
> the one in the dm814x and the one in the am335x. So I think it would
> work to put only the version register offet in the DT, and the let the
> driver figure out the rest from there.

Yes, that's indeed better. We did that for other IPs already (GPIO, I2C...)

> But if TI is planning on reordering the registers with each new
> silicon revision, again and again, then it might make sense to keep
> the offsets in the DT.

Yeah, let's assume they will do a better job in the future.

All these offset registers information does belong to the driver, and 
even if the HW change a lot, I still rather hide that in the driver.
It will always be cleaner, most efficient, and will reduce the size if 
the blob.

> [ I really wonder why the hardware people think that reshuffling the
>    register layout constitutes an improvement. ]

I've been wondering that for ten years :-(
I'm always hoping it will be better some day.

Regards,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Vaibhav Hiremath <hvaibhav@ti.com>,
	netdev@vger.kernel.org, paul@pwsan.com,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Mugunthan V N <mugunthanvnm@ti.com>
Subject: Re: [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX
Date: Thu, 1 Nov 2012 10:28:47 +0100	[thread overview]
Message-ID: <509240CF.6060909@ti.com> (raw)
In-Reply-To: <20121101074508.GA2637@netboy.at.omicron.at>

On 11/1/2012 8:45 AM, Richard Cochran wrote:
> On Wed, Oct 31, 2012 at 04:17:27PM +0100, Benoit Cousson wrote:
>>> +			compatible = "ti,cpsw";
>>> +			ti,hwmods = "cpgmac0";
>>> +			cpdma_channels = <8>;
>>> +			host_port_no = <0>;
>>> +			cpdma_reg_ofs = <0x800>;
>>> +			cpdma_sram_ofs = <0xa00>;
>>> +			ale_reg_ofs = <0xd00>;
>>> +			ale_entries = <1024>;
>>> +			host_port_reg_ofs = <0x108>;
>>> +			hw_stats_reg_ofs = <0x900>;
>>> +			bd_ram_ofs = <0x2000>;
>>> +			bd_ram_size = <0x2000>;
>>> +			no_bd_ram = <0>;
>>> +			rx_descs = <64>;
>>> +			mac_control = <0x20>;
>>
>> Do you have to store all these data in the DTS? Cannot it be in the driver?
>>
>> Do you expect to have several instance of the same IP with different
>> parameters here?
>
> As I understand it, there are only two different layouts for the CPSW,
> the one in the dm814x and the one in the am335x. So I think it would
> work to put only the version register offet in the DT, and the let the
> driver figure out the rest from there.

Yes, that's indeed better. We did that for other IPs already (GPIO, I2C...)

> But if TI is planning on reordering the registers with each new
> silicon revision, again and again, then it might make sense to keep
> the offsets in the DT.

Yeah, let's assume they will do a better job in the future.

All these offset registers information does belong to the driver, and 
even if the HW change a lot, I still rather hide that in the driver.
It will always be cleaner, most efficient, and will reduce the size if 
the blob.

> [ I really wonder why the hardware people think that reshuffling the
>    register layout constitutes an improvement. ]

I've been wondering that for ten years :-(
I'm always hoping it will be better some day.

Regards,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX
Date: Thu, 1 Nov 2012 10:28:47 +0100	[thread overview]
Message-ID: <509240CF.6060909@ti.com> (raw)
In-Reply-To: <20121101074508.GA2637@netboy.at.omicron.at>

On 11/1/2012 8:45 AM, Richard Cochran wrote:
> On Wed, Oct 31, 2012 at 04:17:27PM +0100, Benoit Cousson wrote:
>>> +			compatible = "ti,cpsw";
>>> +			ti,hwmods = "cpgmac0";
>>> +			cpdma_channels = <8>;
>>> +			host_port_no = <0>;
>>> +			cpdma_reg_ofs = <0x800>;
>>> +			cpdma_sram_ofs = <0xa00>;
>>> +			ale_reg_ofs = <0xd00>;
>>> +			ale_entries = <1024>;
>>> +			host_port_reg_ofs = <0x108>;
>>> +			hw_stats_reg_ofs = <0x900>;
>>> +			bd_ram_ofs = <0x2000>;
>>> +			bd_ram_size = <0x2000>;
>>> +			no_bd_ram = <0>;
>>> +			rx_descs = <64>;
>>> +			mac_control = <0x20>;
>>
>> Do you have to store all these data in the DTS? Cannot it be in the driver?
>>
>> Do you expect to have several instance of the same IP with different
>> parameters here?
>
> As I understand it, there are only two different layouts for the CPSW,
> the one in the dm814x and the one in the am335x. So I think it would
> work to put only the version register offet in the DT, and the let the
> driver figure out the rest from there.

Yes, that's indeed better. We did that for other IPs already (GPIO, I2C...)

> But if TI is planning on reordering the registers with each new
> silicon revision, again and again, then it might make sense to keep
> the offsets in the DT.

Yeah, let's assume they will do a better job in the future.

All these offset registers information does belong to the driver, and 
even if the HW change a lot, I still rather hide that in the driver.
It will always be cleaner, most efficient, and will reduce the size if 
the blob.

> [ I really wonder why the hardware people think that reshuffling the
>    register layout constitutes an improvement. ]

I've been wondering that for ten years :-(
I'm always hoping it will be better some day.

Regards,
Benoit

  reply	other threads:[~2012-11-01  9:28 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29  8:21 # (c) 2007, Joe Perches <joe@perches.com> Vaibhav Hiremath
2012-10-29  8:21 ` Vaibhav Hiremath
2012-10-29  8:21 ` Vaibhav Hiremath
2012-10-29  8:21 ` [PATCH-V2 0/4] ARM: AM33XX: net: Add DT support to CPGMAC and MDIO driver Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:33   ` Richard Cochran
2012-10-29  8:33     ` Richard Cochran
2012-10-29  8:21 ` [PATCH 1/4] net: davinci_mdio: Fix typo mistake in calling runtime-pm api Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-30 21:33   ` Peter Korsgaard
2012-10-30 21:33     ` Peter Korsgaard
2012-10-30 21:33     ` Peter Korsgaard
2012-10-29  8:21 ` [PATCH 2/4] net: cpsw: Add parent<->child relation support between cpsw and mdio Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-30 21:34   ` Peter Korsgaard
2012-10-30 21:34     ` Peter Korsgaard
2012-10-30 21:34     ` Peter Korsgaard
2012-10-29  8:21 ` [PATCH 3/4] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio module Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-30 21:35   ` Peter Korsgaard
2012-10-30 21:35     ` Peter Korsgaard
2012-10-30 21:35     ` Peter Korsgaard
2012-10-29  8:21 ` [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-29  8:21   ` Vaibhav Hiremath
2012-10-30 21:35   ` Peter Korsgaard
2012-10-30 21:35     ` Peter Korsgaard
2012-10-30 21:35     ` Peter Korsgaard
2012-10-31 15:17   ` Benoit Cousson
2012-10-31 15:17     ` Benoit Cousson
2012-10-31 15:17     ` Benoit Cousson
2012-10-31 19:52     ` Hiremath, Vaibhav
2012-10-31 19:52       ` Hiremath, Vaibhav
2012-11-01  7:45     ` Richard Cochran
2012-11-01  7:45       ` Richard Cochran
2012-11-01  9:28       ` Cousson, Benoit [this message]
2012-11-01  9:28         ` Cousson, Benoit
2012-11-01  9:28         ` Cousson, Benoit
2012-11-03 17:45         ` [PATCH RFC net-next 0/1] Simplify the CPSW DT Richard Cochran
2012-11-03 17:45           ` Richard Cochran
2012-11-03 17:45           ` Richard Cochran
2012-11-03 17:45           ` [PATCH RFC net-next 1/1] cpsw: simplify the setup of the register pointers Richard Cochran
2012-11-03 17:45             ` Richard Cochran
2012-11-03 17:45             ` Richard Cochran
2012-11-02  8:46     ` [PATCH 4/4] arm/dts: am33xx: Add CPSW and MDIO module nodes for AM33XX N, Mugunthan V
2012-11-02  8:46       ` N, Mugunthan V
2012-11-02  8:56       ` Richard Cochran
2012-11-02  8:56         ` Richard Cochran
2012-11-02 10:42         ` N, Mugunthan V
2012-11-02 10:42           ` N, Mugunthan V
2012-11-02 15:19           ` Richard Cochran
2012-11-02 15:19             ` Richard Cochran
2012-11-08 12:59     ` Mugunthan V N
2012-11-08 12:59       ` Mugunthan V N
2012-11-08 12:59       ` Mugunthan V N
2012-10-29  9:25 ` # (c) 2007, Joe Perches <joe@perches.com> Vaibhav Hiremath
2012-10-29  9:25   ` Vaibhav Hiremath
2012-10-29  9:25   ` Vaibhav Hiremath

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=509240CF.6060909@ti.com \
    --to=b-cousson@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=richardcochran@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.