From: Olof Johansson <olof@lixom.net>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alexandre.belloni@bootlin.com, arnd@arndb.de, soc@kernel.org,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
t-kristo@ti.com, vkoul@kernel.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: defconfig: Enable Texas Instruments UDMA driver
Date: Fri, 24 Jan 2020 12:08:11 -0800 [thread overview]
Message-ID: <20200124200811.ytgs66cg5qpugi5c@localhost> (raw)
In-Reply-To: <20200124092359.12429-1-peter.ujfalusi@ti.com>
On Fri, Jan 24, 2020 at 11:23:59AM +0200, Peter Ujfalusi wrote:
> The UDMA driver is used on K3 platforms (am654 and j721e).
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> Hi,
>
> The drivers for UDMA are already in linu-next and the DT patches are going to be
> also heading for 5.6.
> The only missing piece is to enable the drivers in defconfig so clients can use
> the DMA.
Hi Peter,
We normally like to see new options turned on after the driver/option has been
merged, so send this during or right after the merge window when that happens,
please.
I also see that this is statically enabling this driver -- we try to keep as
many drivers as possible as modules to avoid the static kernel from growing too
large. Would that be a suitable approach here, or is the driver needed to reach
rootfs for further module loading?
Thanks,
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-24 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 9:23 [PATCH] arm64: defconfig: Enable Texas Instruments UDMA driver Peter Ujfalusi
2020-01-24 20:08 ` Olof Johansson [this message]
2020-01-27 10:32 ` Peter Ujfalusi
2020-01-27 15:30 ` Olof Johansson
2020-01-28 8:21 ` Peter Ujfalusi
2020-03-25 14:57 ` Arnd Bergmann
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=20200124200811.ytgs66cg5qpugi5c@localhost \
--to=olof@lixom.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=soc@kernel.org \
--cc=t-kristo@ti.com \
--cc=vkoul@kernel.org \
--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