From: Nishanth Menon <nm@ti.com> To: Rajendra Nayak <rnayak@ti.com> Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, tony@atomide.com, paul@pwsan.com, khilman@linaro.org, benoit.cousson@gmail.com, r.sricharan@ti.com, ambresh@ti.com, sourav.poddar@ti.com Subject: Re: [PATCH v2 8/8] ARM: DRA7: dts: Add the dts files for dra7 SoC and dra7-evm board Date: Tue, 30 Jul 2013 07:59:54 -0500 [thread overview] Message-ID: <51F7B8CA.9050707@ti.com> (raw) In-Reply-To: <51F7B80F.8090202@ti.com> On 07/30/2013 07:56 AM, Rajendra Nayak wrote: > On Tuesday 30 July 2013 06:16 PM, Nishanth Menon wrote: >> On 07/30/2013 07:41 AM, Rajendra Nayak wrote: >>> On Tuesday 30 July 2013 06:00 PM, Nishanth Menon wrote: >>>> On 07/30/2013 06:25 AM, Rajendra Nayak wrote: >>>>> From: R Sricharan <r.sricharan@ti.com> >> [...] >>>>> + mcspi4: spi@480ba000 { >>>>> + compatible = "ti,omap4-mcspi"; >>>>> + reg = <0x480ba000 0x200>; >>>>> + interrupts = <0 48 0x4>; >>>>> + #address-cells = <1>; >>>>> + #size-cells = <0>; >>>>> + ti,hwmods = "mcspi4"; >>>>> + ti,spi-num-cs = <1>; >>>>> + dmas = <&sdma 70>, <&sdma 71>; >>>>> + dma-names = "tx0", "rx0"; >>>>> + }; >>>>> + }; >>>>> +}; >>>>> >>>> ref: [1], we discussed that we should now be able to introduce all instances of h/w blocks into the dra7.dts. Further, considering [2] >>> >>> hmm, thats a long discussion on crossbar driver that [1] points to. Do you want to summarize what you mean by 'introduce all instances of h/w blocks' >> >> I recommend reading the last few emails on the thread about how we could do this with pinctrl. unfortunately, this patch is not informative enough to indicate that not all instances of the potential IP blocks are listed here. >> >>> >>>> would you not want to follow "status = disabled" for all modules by default and enable required modules in board file, so that we dont have to respin this yet again? >>> >>> Well, I was just following the convention of whats already followed on existing OMAPs. See [3] for some views on these. >> >> DRA7 case, I would not think it makes sense due to the number of product variants being done, not all will use the same set. Further, rationale for DRA7 and my suggestion for Grant's option (1) is mainly because the product variants will require more dtsis rather than board files using the product variants use just the necessary modules from a common dtsi. Makes support of variants like OMAP57xx etc trivial and constrainted to board file usage, rather than spinning off new dtsis. > > Makes sense with the different product variants for DRA7, AM335x already does it this way, but the rest of OMAP3/4/5 are doing it the other way. > I think its just too confusing to follow different conventions for different SoCs. We should stick to just one, either this way or that. > I think bucketing DRA7(with multitude of SoC variants) with OMAP family(usually with <5 variants) will be a wrong approach. we should choose the approach appropriate for the SoC. hence, OMAPx having all default enabled makes sense (as the delta is usually trivial), but on DRA7, the variants are larger :( just my 2 cents. >> >>> >>>> >>>> >>>> [1] http://marc.info/?t=137416599400001&r=1&w=2 >>>> [2] http://marc.info/?l=linux-omap&m=137510358229479&w=2 >>> [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/086297.html >>> >> >> > -- Regards, Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 8/8] ARM: DRA7: dts: Add the dts files for dra7 SoC and dra7-evm board Date: Tue, 30 Jul 2013 07:59:54 -0500 [thread overview] Message-ID: <51F7B8CA.9050707@ti.com> (raw) In-Reply-To: <51F7B80F.8090202@ti.com> On 07/30/2013 07:56 AM, Rajendra Nayak wrote: > On Tuesday 30 July 2013 06:16 PM, Nishanth Menon wrote: >> On 07/30/2013 07:41 AM, Rajendra Nayak wrote: >>> On Tuesday 30 July 2013 06:00 PM, Nishanth Menon wrote: >>>> On 07/30/2013 06:25 AM, Rajendra Nayak wrote: >>>>> From: R Sricharan <r.sricharan@ti.com> >> [...] >>>>> + mcspi4: spi at 480ba000 { >>>>> + compatible = "ti,omap4-mcspi"; >>>>> + reg = <0x480ba000 0x200>; >>>>> + interrupts = <0 48 0x4>; >>>>> + #address-cells = <1>; >>>>> + #size-cells = <0>; >>>>> + ti,hwmods = "mcspi4"; >>>>> + ti,spi-num-cs = <1>; >>>>> + dmas = <&sdma 70>, <&sdma 71>; >>>>> + dma-names = "tx0", "rx0"; >>>>> + }; >>>>> + }; >>>>> +}; >>>>> >>>> ref: [1], we discussed that we should now be able to introduce all instances of h/w blocks into the dra7.dts. Further, considering [2] >>> >>> hmm, thats a long discussion on crossbar driver that [1] points to. Do you want to summarize what you mean by 'introduce all instances of h/w blocks' >> >> I recommend reading the last few emails on the thread about how we could do this with pinctrl. unfortunately, this patch is not informative enough to indicate that not all instances of the potential IP blocks are listed here. >> >>> >>>> would you not want to follow "status = disabled" for all modules by default and enable required modules in board file, so that we dont have to respin this yet again? >>> >>> Well, I was just following the convention of whats already followed on existing OMAPs. See [3] for some views on these. >> >> DRA7 case, I would not think it makes sense due to the number of product variants being done, not all will use the same set. Further, rationale for DRA7 and my suggestion for Grant's option (1) is mainly because the product variants will require more dtsis rather than board files using the product variants use just the necessary modules from a common dtsi. Makes support of variants like OMAP57xx etc trivial and constrainted to board file usage, rather than spinning off new dtsis. > > Makes sense with the different product variants for DRA7, AM335x already does it this way, but the rest of OMAP3/4/5 are doing it the other way. > I think its just too confusing to follow different conventions for different SoCs. We should stick to just one, either this way or that. > I think bucketing DRA7(with multitude of SoC variants) with OMAP family(usually with <5 variants) will be a wrong approach. we should choose the approach appropriate for the SoC. hence, OMAPx having all default enabled makes sense (as the delta is usually trivial), but on DRA7, the variants are larger :( just my 2 cents. >> >>> >>>> >>>> >>>> [1] http://marc.info/?t=137416599400001&r=1&w=2 >>>> [2] http://marc.info/?l=linux-omap&m=137510358229479&w=2 >>> [3] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/086297.html >>> >> >> > -- Regards, Nishanth Menon
next prev parent reply other threads:[~2013-07-30 13:00 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-30 11:25 [PATCH v2 0/8] DRA7xx core support Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 1/8] ARM: DRA7: id: Add cpu detection support for DRA7xx based SoCs' Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 13:10 ` Felipe Balbi 2013-07-30 13:10 ` Felipe Balbi 2013-07-30 13:18 ` Felipe Balbi 2013-07-30 13:18 ` Felipe Balbi 2013-07-30 13:55 ` Tony Lindgren 2013-07-30 13:55 ` Tony Lindgren 2013-07-30 14:18 ` Sricharan R 2013-07-30 14:18 ` Sricharan R 2013-07-30 14:23 ` Felipe Balbi 2013-07-30 14:23 ` Felipe Balbi 2013-07-30 14:36 ` Sricharan R 2013-07-30 14:36 ` Sricharan R 2013-07-30 15:32 ` Felipe Balbi 2013-07-30 15:32 ` Felipe Balbi 2013-07-30 18:37 ` Sricharan R 2013-07-30 18:37 ` Sricharan R 2013-07-30 18:43 ` Nishanth Menon 2013-07-30 18:43 ` Nishanth Menon 2013-07-31 6:02 ` Rajendra Nayak 2013-07-31 6:02 ` Rajendra Nayak 2013-07-31 6:42 ` Tony Lindgren 2013-07-31 6:42 ` Tony Lindgren 2013-07-31 6:49 ` Rajendra Nayak 2013-07-31 6:49 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 2/8] ARM: DRA7: hwmod: Reuse the soc_ops used for OMAP4/5 Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 3/8] ARM: DRA7: Reuse all of PRCM and MPUSS SMP infra Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 12:26 ` Nishanth Menon 2013-07-30 12:26 ` Nishanth Menon 2013-07-30 12:38 ` Rajendra Nayak 2013-07-30 12:38 ` Rajendra Nayak 2013-07-30 12:41 ` Nishanth Menon 2013-07-30 12:41 ` Nishanth Menon 2013-07-30 12:48 ` Rajendra Nayak 2013-07-30 12:48 ` Rajendra Nayak 2013-07-30 12:57 ` Nishanth Menon 2013-07-30 12:57 ` Nishanth Menon 2013-07-30 12:59 ` Rajendra Nayak 2013-07-30 12:59 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 4/8] ARM: DRA7: Reuse io tables and add a new .init_early Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 5/8] ARM: DRA7: Resue the clocksource, clockevent support Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 6/8] ARM: DRA7: board-generic: Add basic DT support Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 7/8] ARM: DRA7: Kconfig: Make ARCH_NR_GPIO default to 512 Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 11:25 ` [PATCH v2 8/8] ARM: DRA7: dts: Add the dts files for dra7 SoC and dra7-evm board Rajendra Nayak 2013-07-30 11:25 ` Rajendra Nayak 2013-07-30 12:30 ` Nishanth Menon 2013-07-30 12:30 ` Nishanth Menon 2013-07-30 12:41 ` Rajendra Nayak 2013-07-30 12:41 ` Rajendra Nayak 2013-07-30 12:46 ` Nishanth Menon 2013-07-30 12:46 ` Nishanth Menon 2013-07-30 12:56 ` Rajendra Nayak 2013-07-30 12:56 ` Rajendra Nayak 2013-07-30 12:59 ` Nishanth Menon [this message] 2013-07-30 12:59 ` Nishanth Menon 2013-07-30 13:01 ` Rajendra Nayak 2013-07-30 13:01 ` Rajendra Nayak 2013-08-12 13:46 ` Benoit Cousson 2013-08-12 13:46 ` Benoit Cousson 2013-08-12 11:44 ` Mark Rutland 2013-08-12 11:44 ` Mark Rutland 2013-08-13 7:24 ` Rajendra Nayak 2013-08-13 7:24 ` Rajendra Nayak 2013-08-13 9:46 ` Mark Rutland 2013-08-13 9:46 ` Mark Rutland 2013-08-13 10:05 ` Marc Zyngier 2013-08-13 10:05 ` Marc Zyngier 2013-08-14 9:40 ` Rajendra Nayak 2013-08-14 9:40 ` Rajendra Nayak 2013-08-02 22:28 ` [PATCH v2 0/8] DRA7xx core support Santosh Shilimkar 2013-08-02 22:28 ` Santosh Shilimkar 2013-08-04 16:14 ` Rajendra Nayak 2013-08-04 16:14 ` 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=51F7B8CA.9050707@ti.com \ --to=nm@ti.com \ --cc=ambresh@ti.com \ --cc=benoit.cousson@gmail.com \ --cc=khilman@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.com \ --cc=r.sricharan@ti.com \ --cc=rnayak@ti.com \ --cc=sourav.poddar@ti.com \ --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: linkBe 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.