From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/12] ARM: DRA7: hwmod: Create initial DRA7XX SoC data
Date: Tue, 9 Jul 2013 04:36:57 -0700 [thread overview]
Message-ID: <20130709113657.GF5523@atomide.com> (raw)
In-Reply-To: <51DBE2A2.2040403@ti.com>
* Rajendra Nayak <rnayak@ti.com> [130709 03:21]:
> On Tuesday 09 July 2013 02:01 PM, Tony Lindgren wrote:
> > * Rajendra Nayak <rnayak@ti.com> [130709 00:39]:
> >> From: Ambresh K <ambresh@ti.com>
> >
> >> --- /dev/null
> >> +++ b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
> > ...
> >
> >> +/* dma_system */
> >> +static struct omap_hwmod_irq_info dra7xx_dma_system_irqs[] = {
> >> + { .name = "0", .irq = 12 + DRA7XX_IRQ_GIC_START },
> >> + { .name = "1", .irq = 13 + DRA7XX_IRQ_GIC_START },
> >> + { .name = "2", .irq = 14 + DRA7XX_IRQ_GIC_START },
> >> + { .name = "3", .irq = 15 + DRA7XX_IRQ_GIC_START },
> >> + { .irq = -1 }
> >> +};
> >
> > I think these should no longer be needed?
>
> These are needed only for dma because mach-omap2/dma.c still creates
> devices from hmwod and which are used by plat/dma.c.
> These irqs for sdma exist even in the cleaned up omap4 and omap5 hmwod files.
> I'll try and get rid of that dependency of plat/dma on mach/dma to create devices.
OK great.
> > In general, we must move the hwmod stuff to drivers/bus and start
> > parsing the data from device tree along the lines Tero is doing
> > for the clock data.
>
> We already have irq/dma and iospace moved to DT (some iospace info still
> exists because of non-DT drivers). With Teros patches to move clock data we
> should be able to pass the main_clk and all interface level clock info too
> from DT.
OK.
Tony
next prev parent reply other threads:[~2013-07-09 11:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 7:32 [PATCH 00/12] DRA7xx PRCM, hwmod and DT data Rajendra Nayak
2013-07-09 7:32 ` [PATCH 01/12] ARM: DRA7: PRM: Add DRA7XX register definitions Rajendra Nayak
2013-07-09 7:32 ` [PATCH 02/12] ARM: DRA7: CM: Add DRA7XX register defines Rajendra Nayak
2013-07-09 7:32 ` [PATCH 03/12] ARM: DRA7: CM: Add minimal regbit shifts Rajendra Nayak
2013-07-09 7:32 ` [PATCH 04/12] ARM: DRA7: PRCM: Add DRA7XX local MPU PRCM regsiters Rajendra Nayak
2013-07-09 7:32 ` [PATCH 05/12] ARM: DRA7: clockdomain: Add DRA7XX data and update header Rajendra Nayak
2013-07-09 7:32 ` [PATCH 06/12] ARM: DRA7: powerdomain: " Rajendra Nayak
2013-07-09 7:32 ` [PATCH 07/12] ARM: DRA7: powerdomain: Handle missing vc/vp Rajendra Nayak
2013-07-09 7:32 ` [PATCH 08/12] ARM: DRA7: Reuse the omap44xx_restart and fix the device instance Rajendra Nayak
2013-07-14 12:12 ` Kevin Hilman
2013-07-09 7:32 ` [PATCH 09/12] ARM: DRA7: hwmod: Create initial DRA7XX SoC data Rajendra Nayak
2013-07-09 8:31 ` Tony Lindgren
2013-07-09 10:14 ` Rajendra Nayak
2013-07-09 11:36 ` Tony Lindgren [this message]
2013-07-15 9:22 ` Rajendra Nayak
2013-07-09 7:32 ` [PATCH 10/12] ARM: DRA7: Enable PM framework initializations Rajendra Nayak
2013-07-09 7:32 ` [PATCH 11/12] ARM: DRA7: Add the build support in omap2plus Rajendra Nayak
2013-07-09 7:32 ` [PATCH 12/12] ARM: DRA7: dts: Add the dts files for dra7 SoC and dra7-evm board Rajendra Nayak
2013-08-21 2:10 ` [PATCH 00/12] DRA7xx PRCM, hwmod and DT data Paul Walmsley
2013-08-21 8:55 ` Paul Walmsley
2013-08-21 9:16 ` Rajendra Nayak
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=20130709113657.GF5523@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).