From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags
Date: Wed, 23 Sep 2015 11:19:32 -0700 [thread overview]
Message-ID: <5602ED34.9010108@oracle.com> (raw)
In-Reply-To: <1442938118-4718-2-git-send-email-nm@ti.com>
Nishant,
On 9/22/2015 9:08 AM, Nishanth Menon wrote:
> Keystone2 devices are used on more platforms than just Texas
> Instruments reference evaluation platforms called EVMs. Providing a
> generic compatible "ti,keystone" is not sufficient to differentiate
> various SoC definitions possible on various platforms. So, provide
> compatible matches for each SoC family by itself.
>
> This allows SoC specific logic to be run time handled based on
> of_machine_is_compatible("ti,k2hk") or as needed for the dependent
> processor instead of needing to use board dependent compatibles that
> are needed now.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
You need to expand that 'not sufficient' for me. Unless there is
genuine case to support this, I would want to avoid this churn.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh shilimkar <santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>,
Santosh Shilimkar
<ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags
Date: Wed, 23 Sep 2015 11:19:32 -0700 [thread overview]
Message-ID: <5602ED34.9010108@oracle.com> (raw)
In-Reply-To: <1442938118-4718-2-git-send-email-nm-l0cyMroinI0@public.gmane.org>
Nishant,
On 9/22/2015 9:08 AM, Nishanth Menon wrote:
> Keystone2 devices are used on more platforms than just Texas
> Instruments reference evaluation platforms called EVMs. Providing a
> generic compatible "ti,keystone" is not sufficient to differentiate
> various SoC definitions possible on various platforms. So, provide
> compatible matches for each SoC family by itself.
>
> This allows SoC specific logic to be run time handled based on
> of_machine_is_compatible("ti,k2hk") or as needed for the dependent
> processor instead of needing to use board dependent compatibles that
> are needed now.
>
> Signed-off-by: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
> ---
You need to expand that 'not sufficient' for me. Unless there is
genuine case to support this, I would want to avoid this churn.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Nishanth Menon <nm@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags
Date: Wed, 23 Sep 2015 11:19:32 -0700 [thread overview]
Message-ID: <5602ED34.9010108@oracle.com> (raw)
In-Reply-To: <1442938118-4718-2-git-send-email-nm@ti.com>
Nishant,
On 9/22/2015 9:08 AM, Nishanth Menon wrote:
> Keystone2 devices are used on more platforms than just Texas
> Instruments reference evaluation platforms called EVMs. Providing a
> generic compatible "ti,keystone" is not sufficient to differentiate
> various SoC definitions possible on various platforms. So, provide
> compatible matches for each SoC family by itself.
>
> This allows SoC specific logic to be run time handled based on
> of_machine_is_compatible("ti,k2hk") or as needed for the dependent
> processor instead of needing to use board dependent compatibles that
> are needed now.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
You need to expand that 'not sufficient' for me. Unless there is
genuine case to support this, I would want to avoid this churn.
Regards,
Santosh
next prev parent reply other threads:[~2015-09-23 18:19 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:08 [PATCH 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-23 18:05 ` Murali Karicheri
2015-09-23 18:05 ` Murali Karicheri
2015-09-23 18:05 ` Murali Karicheri
2015-09-23 19:15 ` Nishanth Menon
2015-09-23 19:15 ` Nishanth Menon
2015-09-23 19:15 ` Nishanth Menon
2015-09-23 18:19 ` santosh shilimkar [this message]
2015-09-23 18:19 ` santosh shilimkar
2015-09-23 18:19 ` santosh shilimkar
2015-09-24 14:05 ` Murali Karicheri
2015-09-24 14:05 ` Murali Karicheri
2015-09-24 14:05 ` Murali Karicheri
2015-09-24 14:20 ` Nishanth Menon
2015-09-24 14:20 ` Nishanth Menon
2015-09-24 14:20 ` Nishanth Menon
2015-09-24 15:54 ` Murali Karicheri
2015-09-24 15:54 ` Murali Karicheri
2015-09-24 15:54 ` Murali Karicheri
2015-09-25 14:50 ` Nishanth Menon
2015-09-25 14:50 ` Nishanth Menon
2015-09-25 14:50 ` Nishanth Menon
2015-09-25 15:18 ` santosh shilimkar
2015-09-25 15:18 ` santosh shilimkar
2015-09-25 16:01 ` Nishanth Menon
2015-09-25 16:01 ` Nishanth Menon
2015-09-25 16:01 ` Nishanth Menon
2015-09-25 16:15 ` santosh shilimkar
2015-09-25 16:15 ` santosh shilimkar
2015-09-25 16:15 ` santosh shilimkar
2015-09-25 17:38 ` Nishanth Menon
2015-09-25 17:38 ` Nishanth Menon
2015-09-25 17:38 ` Nishanth Menon
2015-10-02 16:09 ` santosh shilimkar
2015-10-02 16:09 ` santosh shilimkar
2015-10-03 23:44 ` Nishanth Menon
2015-10-03 23:44 ` Nishanth Menon
2015-10-03 23:44 ` Nishanth Menon
2015-10-04 0:16 ` santosh.shilimkar at oracle.com
2015-10-04 0:16 ` santosh.shilimkar
2015-10-04 0:16 ` santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA
2015-09-30 14:31 ` Murali Karicheri
2015-09-30 14:31 ` Murali Karicheri
2015-09-30 14:31 ` Murali Karicheri
2015-09-22 16:08 ` [PATCH 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` [PATCH 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-09-22 16:08 ` Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon
2015-10-04 0:13 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches santosh.shilimkar at oracle.com
2015-10-04 0:13 ` santosh.shilimkar
2015-10-04 0:13 ` santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA
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=5602ED34.9010108@oracle.com \
--to=santosh.shilimkar@oracle.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 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.