[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3764397-ec79-0bb6-e3f4-179f92e1e45c@ti.com>
Date: Wed, 2 Aug 2023 11:33:16 -0500
From: Andrew Davis <afd@...com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Arnd Bergmann <arnd@...db.de>,
Christian Gmeiner <christian.gmeiner@...il.com>,
John Stultz <jstultz@...gle.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Sumit Semwal <sumit.semwal@...aro.org>,
<linux-media@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<linaro-mm-sig@...ts.linaro.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] misc: sram: Add DMA-BUF Heap exporting of SRAM areas
On 7/13/23 2:27 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 13, 2023 at 02:13:16PM -0500, Andrew Davis wrote:
>> +int sram_add_dma_heap(struct sram_dev *sram,
>> + struct sram_reserve *block,
>> + phys_addr_t start,
>> + struct sram_partition *part)
>> +{
>> + struct sram_dma_heap *sram_dma_heap;
>> + struct dma_heap_export_info exp_info;
>> +
>> + dev_info(sram->dev, "Exporting SRAM Heap '%s'\n", block->label);
>
> When drivers are working properly, they are quiet.
>
This should only be printed once in early boot when the memory is added,
I was wanting this to match the other memory exporters/output at the
beginning of boot logs.
But quiet is fine too, will change this to dev_dbg() for v4.
Thanks,
Andrew
> thanks,
>
> greg k-h
Powered by blists - more mailing lists