From: Nishanth Menon <nm@ti.com>
To: Suman Anna <s-anna@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Dave Gerlach <d-gerlach@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Kishon Vijay Abraham <kishon@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH v3 3/5] arm64: dts: ti: Add support for AM642 SoC
Date: Thu, 21 Jan 2021 14:13:44 -0600 [thread overview]
Message-ID: <20210121201344.amp54x6d5fty7rkf@shriek> (raw)
In-Reply-To: <2b35fb8b-0477-f66d-bcbd-ad640664a888@ti.com>
On 13:57-20210121, Suman Anna wrote:
> This is all moot when your own tree doesn't boot properly. In this case, you are
> adding MMC nodes, but yet for a boot test, you are saying use linux-next for the
> nodes that were added or you need additional driver patches (which is not how
> maintainer-level trees are verified).
Get your facts straight please.
What do you mean does'nt boot? It does boot with initramfs which is
the minimum qual i had set for any new platform (along with. - your
need is for a device node to work - which is both a combination of
defconfig + driver updates.
>
> Arnd,
> Can you please guide us here as to what is expected in general, given that the
> pull-request from Nishanth goes through you, and if there is some pre-existing
> norms around this?
>
> Tony,
> Appreciate your input as well since you probably have dealt with these kinda of
> dependencies on OMAP.
I am more than happy to drop this entire SoC off my queue (I am yet to
pick it up), which is probably what I will do.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2021-01-21 20:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:25 [PATCH v3 0/5] arm64: Initial support for Texas Instruments AM642 Platform Dave Gerlach
2021-01-20 20:25 ` [PATCH v3 1/5] dt-bindings: arm: ti: Add bindings for AM642 SoC Dave Gerlach
2021-01-20 20:25 ` [PATCH v3 2/5] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM64 Dave Gerlach
2021-01-20 20:50 ` Suman Anna
2021-01-25 14:39 ` Nishanth Menon
2021-02-09 2:34 ` Rob Herring
2021-01-20 20:25 ` [PATCH v3 3/5] arm64: dts: ti: Add support for AM642 SoC Dave Gerlach
2021-01-20 22:04 ` Nishanth Menon
2021-01-21 17:25 ` Suman Anna
2021-01-21 17:46 ` Nishanth Menon
2021-01-21 18:13 ` Suman Anna
2021-01-21 18:39 ` Nishanth Menon
2021-01-21 19:57 ` Suman Anna
2021-01-21 20:13 ` Nishanth Menon [this message]
2021-01-21 20:42 ` Suman Anna
2021-01-21 21:18 ` Nishanth Menon
2021-01-21 22:57 ` Suman Anna
2021-01-22 11:23 ` Arnd Bergmann
2021-01-22 13:00 ` Tony Lindgren
2021-01-25 14:16 ` Nishanth Menon
2021-01-25 22:48 ` Suman Anna
2021-01-25 23:02 ` Suman Anna
2021-01-20 20:25 ` [PATCH v3 4/5] arm64: dts: ti: k3-am64-main: Enable DMA support Dave Gerlach
2021-01-20 20:25 ` [PATCH v3 5/5] arm64: dts: ti: Add support for AM642 EVM Dave Gerlach
2021-01-25 16:44 ` Suman Anna
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=20210121201344.amp54x6d5fty7rkf@shriek \
--to=nm@ti.com \
--cc=a-govindraju@ti.com \
--cc=arnd@arndb.de \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox