Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 24 Jan 2020 12:08:11 -0800
From:   Olof Johansson <olof@lixom.net>
To:     Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc:     catalin.marinas@arm.com, will@kernel.org,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        t-kristo@ti.com, vkoul@kernel.org, alexandre.belloni@bootlin.com,
        arnd@arndb.de, soc@kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Texas Instruments UDMA driver
Message-ID: <20200124200811.ytgs66cg5qpugi5c@localhost>
References: <20200124092359.12429-1-peter.ujfalusi@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200124092359.12429-1-peter.ujfalusi@ti.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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