[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4798B4F3.2010101@freescale.com>
Date: Thu, 24 Jan 2008 09:55:31 -0600
From: Timur Tabi <timur@...escale.com>
To: avorontsov@...mvista.com
CC: Poonam_Aggrwal-b10812 <b10812@...escale.com>,
kumar.gala@...escale.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
rubini@...ion.unipv.it, linuxppc-dev@...abs.org,
michael.barkowski@...escale.com, rich.cutler@...escale.com,
ashish.kalra@...escale.com
Subject: Re: [PATCH UCC TDM 1/3 Updated] Platform changes for UCC TDM driver
for MPC8323eRDB. Also includes related QE changes and dts entries.
Anton Vorontsov wrote:
> Can we not introduce new pio-maps in the device trees? There
> were debates regarding this, and if I understood everything
> correctly, pio-maps considered as a bad taste. Better
> do bunch of par_io_config_pin() in the board file. Better
> yet fixup the firmware (u-boot) to set up dedicated pins
> correctly.
I'm on the fence with respect to pio-maps vs. par_io_config_pin() calls. The
problem is that the configuration of these pins is board-specific, but pins are
used by devices. A device driver can't call par_io_config_pin(), because the
calls are different depending on which SoC and which UCC you're using. The
platform code can't call par_io_config_pin(), because that configuration depends
on which drivers are loaded.
In other words, the pin configurations are dependent on the UCC configurations,
and the UCC configurations are stored in the device tree. So it makes sense to
put the pin configurations in the device tree, too.
--
Timur Tabi
Linux kernel developer at Freescale
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists