All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux@arm.linux.org.uk, linux-doc@vger.kernel.org,
	tony@atomide.com, linus.walleij@linaro.org,
	Rajendra Nayak <rnayak@ti.com>,
	linux-kernel@vger.kernel.org, Sricharan R <r.sricharan@ti.com>,
	galak@codeaurora.org, marc.zyngier@arm.com, tglx@linutronix.de,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	grant.likely@linaro.org
Subject: Re: [PATCH V3 7/7] ARM: DRA: Enable Crossbar IP support for DRA7XX
Date: Wed, 13 Nov 2013 11:04:46 -0500	[thread overview]
Message-ID: <5283A31E.4070302@ti.com> (raw)
In-Reply-To: <52839B9C.8090707@ti.com>

On Wednesday 13 November 2013 10:32 AM, Nishanth Menon wrote:
> On 11/11/2013 11:47 PM, Sricharan R wrote:
[..]

> 
> Rationale - with more TI SoCs trending towards crossbar, we dont need
> to keep adding to the soc_is checks, further, we intend to remove
> soc_is checks in it's entirety..
> 
Just for record, and thats what am pushing the TI hardware folks is not to
build default IRQ configuration considering the software will clean-up the
mess. So hope is that we don't have to use this infrastructure always but
only for exceptional cases.

Regards,
Santosh

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 7/7] ARM: DRA: Enable Crossbar IP support for DRA7XX
Date: Wed, 13 Nov 2013 11:04:46 -0500	[thread overview]
Message-ID: <5283A31E.4070302@ti.com> (raw)
In-Reply-To: <52839B9C.8090707@ti.com>

On Wednesday 13 November 2013 10:32 AM, Nishanth Menon wrote:
> On 11/11/2013 11:47 PM, Sricharan R wrote:
[..]

> 
> Rationale - with more TI SoCs trending towards crossbar, we dont need
> to keep adding to the soc_is checks, further, we intend to remove
> soc_is checks in it's entirety..
> 
Just for record, and thats what am pushing the TI hardware folks is not to
build default IRQ configuration considering the software will clean-up the
mess. So hope is that we don't have to use this infrastructure always but
only for exceptional cases.

Regards,
Santosh

WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Sricharan R <r.sricharan@ti.com>, Rajendra Nayak <rnayak@ti.com>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-doc@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-omap@vger.kernel.org>, <linus.walleij@linaro.org>,
	<linux@arm.linux.org.uk>, <tony@atomide.com>,
	<marc.zyngier@arm.com>, <grant.likely@linaro.org>,
	<mark.rutland@arm.com>, <robherring2@gmail.com>,
	<tglx@linutronix.de>, <galak@codeaurora.org>
Subject: Re: [PATCH V3 7/7] ARM: DRA: Enable Crossbar IP support for DRA7XX
Date: Wed, 13 Nov 2013 11:04:46 -0500	[thread overview]
Message-ID: <5283A31E.4070302@ti.com> (raw)
In-Reply-To: <52839B9C.8090707@ti.com>

On Wednesday 13 November 2013 10:32 AM, Nishanth Menon wrote:
> On 11/11/2013 11:47 PM, Sricharan R wrote:
[..]

> 
> Rationale - with more TI SoCs trending towards crossbar, we dont need
> to keep adding to the soc_is checks, further, we intend to remove
> soc_is checks in it's entirety..
> 
Just for record, and thats what am pushing the TI hardware folks is not to
build default IRQ configuration considering the software will clean-up the
mess. So hope is that we don't have to use this infrastructure always but
only for exceptional cases.

Regards,
Santosh


  parent reply	other threads:[~2013-11-13 16:04 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 13:14 [PATCH V3 0/7] DRIVERS: IRQCHIP: Add support for crossbar IP Sricharan R
2013-11-05 13:14 ` Sricharan R
2013-11-05 13:14 ` Sricharan R
2013-11-05 13:14 ` [PATCH V3 1/7] DRIVERS: IRQCHIP: IRQ-GIC: Add support for routable irqs Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-05 13:14   ` Sricharan R
     [not found]   ` <1383657257-3458-2-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2013-11-13 15:24     ` Santosh Shilimkar
2013-11-13 15:24       ` Santosh Shilimkar
2013-11-13 15:24       ` Santosh Shilimkar
2013-11-13 15:32       ` Sricharan R
2013-11-13 15:32         ` Sricharan R
2013-11-13 15:32         ` Sricharan R
2013-11-05 13:14 ` [PATCH V3 2/7] DRIVERS: IRQCHIP: CROSSBAR: Add support for Crossbar IP Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-13 15:27   ` Santosh Shilimkar
2013-11-13 15:27     ` Santosh Shilimkar
2013-11-13 15:27     ` Santosh Shilimkar
2013-11-05 13:14 ` [PATCH V3 3/7] ARM: DTS: DRA: Add crossbar device binding Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-13 15:27   ` Santosh Shilimkar
2013-11-13 15:27     ` Santosh Shilimkar
2013-11-13 15:27     ` Santosh Shilimkar
2013-11-05 13:14 ` [PATCH V3 4/7] ARM: DTS: DRA: Replace peripheral interrupt numbers with crossbar inputs Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-13 15:29   ` Santosh Shilimkar
2013-11-13 15:29     ` Santosh Shilimkar
2013-11-13 15:29     ` Santosh Shilimkar
     [not found] ` <1383657257-3458-1-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2013-11-05 13:14   ` [PATCH V3 5/7] ARM: DTS: DRA7: Add routable-irqs property for gic node Sricharan R
2013-11-05 13:14     ` Sricharan R
2013-11-05 13:14     ` Sricharan R
2013-11-13 15:29     ` Santosh Shilimkar
2013-11-13 15:29       ` Santosh Shilimkar
2013-11-13 15:29       ` Santosh Shilimkar
2013-11-05 13:14   ` [PATCH V3 6/7] ARM: OMAP4+: Correct Wakeup-gen code to use physical irq number Sricharan R
2013-11-05 13:14     ` Sricharan R
2013-11-05 13:14     ` Sricharan R
2013-11-13 15:29     ` Santosh Shilimkar
2013-11-13 15:29       ` Santosh Shilimkar
2013-11-13 15:29       ` Santosh Shilimkar
2013-11-05 13:14 ` [PATCH V3 7/7] ARM: DRA: Enable Crossbar IP support for DRA7XX Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-05 13:14   ` Sricharan R
2013-11-12  5:41   ` Rajendra Nayak
2013-11-12  5:41     ` Rajendra Nayak
2013-11-12  5:41     ` Rajendra Nayak
2013-11-12  5:47     ` Sricharan R
2013-11-12  5:47       ` Sricharan R
2013-11-12  5:47       ` Sricharan R
     [not found]       ` <5281C0E9.8020104-l0cyMroinI0@public.gmane.org>
2013-11-13 15:32         ` Nishanth Menon
2013-11-13 15:32           ` Nishanth Menon
2013-11-13 15:32           ` Nishanth Menon
2013-11-13 15:35           ` Sricharan R
2013-11-13 15:35             ` Sricharan R
2013-11-13 15:35             ` Sricharan R
2013-11-13 16:04           ` Santosh Shilimkar [this message]
2013-11-13 16:04             ` Santosh Shilimkar
2013-11-13 16:04             ` Santosh Shilimkar
2013-11-13 15:30   ` Santosh Shilimkar
2013-11-13 15:30     ` Santosh Shilimkar
2013-11-13 15:30     ` Santosh Shilimkar

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=5283A31E.4070302@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=r.sricharan@ti.com \
    --cc=rnayak@ti.com \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.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.