Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on char-misc/char-misc-testing
char-misc/char-misc-next char-misc/char-misc-linus usb/usb-testing usb/usb-next
usb/usb-linus xen-tip/linux-next linus/master v6.15-r
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on char-misc/char-misc-testing
char-misc/char-misc-next char-misc/char-misc-linus usb/usb-testing usb/usb-next
usb/usb-linus xen-tip/linux-next linus/master v6.15-r
On 4/30/25 16:13, oushixiong wrote:
>
> 在 2025/4/30 19:03, Christian König 写道:
>> On 4/30/25 10:56,oushixiong1...@163.com wrote:
>>> From: Shixiong Ou
>>>
>>> [WHY]
>>> On some boards, the dma_mask of Aspeed devices is 0x_, this
>>> quite possibly causes the SWIOTLB to be triggered when im
在 2025/4/30 19:03, Christian König 写道:
On 4/30/25 10:56,oushixiong1...@163.com wrote:
From: Shixiong Ou
[WHY]
On some boards, the dma_mask of Aspeed devices is 0x_, this
quite possibly causes the SWIOTLB to be triggered when importing dmabuf.
However IO_TLB_SEGSIZE limits the maximum a
On 4/30/25 10:56, oushixiong1...@163.com wrote:
> From: Shixiong Ou
>
> [WHY]
> On some boards, the dma_mask of Aspeed devices is 0x_, this
> quite possibly causes the SWIOTLB to be triggered when importing dmabuf.
> However IO_TLB_SEGSIZE limits the maximum amount of available memory
> f
