From: "Kumar, Udit" <u-kumar1@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: <vigneshr@ti.com>, <catalin.marinas@arm.com>, <will@kernel.org>,
<quic_bjorande@quicinc.com>, <arnd@arndb.de>,
<geert+renesas@glider.be>, <krzysztof.kozlowski@linaro.org>,
<nfraprado@collabora.com>, <rafal@milecki.pl>, <peng.fan@nxp.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Aradhya Bhatia <a-bhatia1@ti.com>,
Hari Nagalla <hnagalla@ti.com>,
MD Danish Anwar <danishanwar@ti.com>,
Jayesh Choudhary <j-choudhary@ti.com>, Judith Mendez <jm@ti.com>,
<u-kumar1@ti.com>
Subject: Re: [PATCH v2] arm64: defconfig: Enable various configs for TI platforms
Date: Wed, 26 Jul 2023 19:38:51 +0530 [thread overview]
Message-ID: <ace112fe-978c-a518-2be5-3f3d1f7fd29c@ti.com> (raw)
In-Reply-To: <20230726134322.gepflrrdcpx6uxvu@colony>
Thanks Nishanth
On 7/26/2023 7:13 PM, Nishanth Menon wrote:
> on $subject: I think mentioning K3 will help narrow things down a bit.
>
> On 19:00-20230726, Udit Kumar wrote:
>> Enable TI ECAP, DP83869 driver, TI OMAP2, K3 remote proc
> I think you mean to state TI mailbox and not omap2 :)
Not really :)
This driver TI OMAP2, (CONFIG_OMAP2PLUS_MBOX) is used in
TI K3 platforms as well for communications with remote processors.
Rest comments will address in v3.
>
>> SND_SOC_J721E_EVM, MCAN, UFS and RTI driver to be built
>> as module.
>> These are needed on different TI platforms.
> Please elaborate the list of boards this benefits TI platforms are a
> big variant list. TI Platforms is too generic a term that scales
> architectures.. that is not the point you are trying to make.
>> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
>> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
>> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
>> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
>> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> If the various contributers are ok, just my 2 cents:
> Could you drop all other sign-offs other than yours? I understand the
> contributions from various members on the TI SDK tree, but I'vent seen
> them attempt to upstream and you took the effort in ensuring the new
> squashed patch contains all the relevant components.
>
> [..]
next prev parent reply other threads:[~2023-07-26 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 13:30 Udit Kumar
2023-07-26 13:43 ` Nishanth Menon
2023-07-26 14:08 ` Kumar, Udit [this message]
2023-07-26 14:15 ` Nishanth Menon
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=ace112fe-978c-a518-2be5-3f3d1f7fd29c@ti.com \
--to=u-kumar1@ti.com \
--cc=a-bhatia1@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=danishanwar@ti.com \
--cc=geert+renesas@glider.be \
--cc=hnagalla@ti.com \
--cc=j-choudhary@ti.com \
--cc=jm@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=peng.fan@nxp.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=vigneshr@ti.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®