linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file
Date: Mon, 10 Jun 2013 07:14:51 -0700	[thread overview]
Message-ID: <20130610141451.GE8164@atomide.com> (raw)
In-Reply-To: <51B5ACA6.2010101@iki.fi>

* Tomi Valkeinen <tomi.valkeinen@iki.fi> [130610 03:44]:
> On 07/06/13 20:50, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [130607 09:35]:
> >> * Paul Walmsley <paul@pwsan.com> [130607 05:38]:
> >>> On Fri, 7 Jun 2013, Sricharan R wrote:
> >>>
> >>>> - 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 <santosh.shilimkar@ti.com>
> >>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
> >>>
> >>> 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

  reply	other threads:[~2013-06-10 14:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 11:56 [PATCH V2 14/14] ARM: OMAP4: hwmod data: Clean up the data file Sricharan R
2013-06-07 12:32 ` Paul Walmsley
2013-06-07 16:29   ` Tony Lindgren
2013-06-07 17:50     ` Tony Lindgren
2013-06-07 18:10       ` Paul Walmsley
2013-06-07 18:14         ` Santosh Shilimkar
2013-06-07 18:37           ` Tony Lindgren
2013-06-07 18:14       ` Santosh Shilimkar
2013-06-07 18:37         ` Tony Lindgren
2013-06-07 18:44           ` Santosh Shilimkar
2013-06-08 16:46             ` Sricharan R
2013-06-08 16:57               ` Tony Lindgren
2013-06-08 17:21                 ` Shilimkar, Santosh
2013-06-08 17:42                   ` Tony Lindgren
2013-06-10 10:38       ` Tomi Valkeinen
2013-06-10 14:14         ` Tony Lindgren [this message]
2013-06-11  7:42           ` Tomi Valkeinen
2013-06-12 13:54             ` Tony Lindgren

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=20130610141451.GE8164@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).