Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1232878
| From | santosh shilimkar <santosh.shilimkar@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags |
| Date | 2015-09-25 17:20 +0200 |
| Message-ID | <qcCX0-58P-11@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <qbWXM-3MS-9@gated-at.bofh.it> <qcfnI-5il-19@gated-at.bofh.it> <qcfH3-5F3-3@gated-at.bofh.it> <qch69-7ye-13@gated-at.bofh.it> <qcCDE-4wT-17@gated-at.bofh.it> |
| Organization | Oracle Corporation |
On 9/25/2015 7:50 AM, Nishanth Menon wrote: > On 09/24/2015 10:54 AM, Murali Karicheri wrote: > [...] >> ti,omap3 is the family of omap3 devices similar to keystone. ti,omap3450 >> is required if there is an exceptional treatment required for ti,omap3450. >> >> In keystone case so far there is no case of exceptional treatment >> required in the code for a specific SoC. So a generic name, ti,keystone >> is used. When exceptional treatment is needed in the future, for example >> k2hk Soc, we should introduce SoC specific string in the following order. > > Did you do a grep on the code to see? > $ git grep ti,omap3 arch/arm/mach-omap2/ > arch/arm/mach-omap2/board-generic.c: "ti,omap3430", > arch/arm/mach-omap2/board-generic.c: "ti,omap3", > arch/arm/mach-omap2/board-generic.c: "ti,omap36xx", > arch/arm/mach-omap2/board-generic.c: "ti,omap3-beagle", > > This is the same as keystone's device support. even though only 36xx was > needed, we introduced other SoC specific compatibility match. > >> "ti,k2hk-evm", "ti,k2hk", "ti,keystone" >> >> So unless there is an exception, there is no need for a SoC specific >> string in the compatibility string list. So this can be added later if >> there is need for exceptional treatment. Did I get it wrong? >> > > I see both your views seem to be "if we dont need a compatible" dont add > it. My view was based on "be accurate in the hardware description" > > OK - i will probably agree on the topic. But, how about userspace > needing to know which SoC they are on, without needing to depend on > board->soc mapping? How do we help resolve that? > Why the user space should care about exact SOC ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-09-22 18:10 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Murali Karicheri <m-karicheri2@ti.com> - 2015-09-23 20:10 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-09-23 21:20 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags santosh shilimkar <santosh.shilimkar@oracle.com> - 2015-09-23 20:30 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Murali Karicheri <m-karicheri2@ti.com> - 2015-09-24 16:10 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-09-24 16:30 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Murali Karicheri <m-karicheri2@ti.com> - 2015-09-24 18:00 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-09-25 17:00 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags santosh shilimkar <santosh.shilimkar@oracle.com> - 2015-09-25 17:20 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-09-25 18:10 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags santosh shilimkar <santosh.shilimkar@oracle.com> - 2015-09-25 18:20 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <menon.nishanth@gmail.com> - 2015-09-25 19:40 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags santosh shilimkar <santosh.shilimkar@oracle.com> - 2015-10-02 18:20 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-10-04 01:50 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com> - 2015-10-04 02:20 +0200
Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Murali Karicheri <m-karicheri2@ti.com> - 2015-09-30 16:40 +0200
csiph-web