* Tomi Valkeinen [off-list ref] [130610 03:44]:

On 07/06/13 20:50, Tony Lindgren wrote:

quoted

* Tony Lindgren [off-list ref] [130607 09:35]:

quoted

* Paul Walmsley [off-list ref] [130607 05:38]:

quoted

On Fri, 7 Jun 2013, Sricharan R wrote:

quoted

- The IO resource information like dma request lines, irq number and
  ocp address space can be populated via dt blob. So such data is stripped
  from OMAP4 SOC hwmod data file.

- The devices which are still missing the device tree bindings,
  address space entries are not removed yet. When such devices add
  the dt bindings, respective address space data can be deleted.

- Also other unnecessary hwmods like firewalls are removed as a part of this.
  Since emif was getting registered only because of this firewalls links,
  the mpu->emif direct link is added now.

The above update, results in reduction of about ~1650 lines of code.

Signed-off-by: Santosh Shilimkar <redacted>
Signed-off-by: Sricharan R <redacted>

Acked-by: Paul Walmsley <paul@pwsan.com>

Can't test this one since I don't have an OMAP4 DT config set up in the testbed
yet.  Maybe will add that to the testbed after the v3.10 release.

OK thanks, applying into omap-for-v3.11/cleanup.

I had to undo the following parts to avoid regressions on omap4sdp.
Can you please follow up on fixing the related issues so the fixup
won't be needed?

Seems to work now the same way as earlier for both omap4sdp and blaze
es, except for DSS, which seems to be a separate issue as posted by
Tomi. Pushed out now to omap-for-v3.11/cleanup.

What issue do you refer to?

DSS does not have DT bindings, and removing DSS from hwmod data will
break DSS for omap4.

Ah that's right. Care to post a patch reverting the minimal parts that
you need for omap4 against omap-for-v3.11/cleanup?

Regards,

Tony