Displaying 3 results from an estimated 3 matches for "ttm_device_init_flag".
Did you mean:
ttm_device_init_flags
2024 Oct 04
1
[PATCH v2 1/2] drm/ttm: Change ttm_device_init to use a struct instead of multiple bools
...v)->anon_inode-
> > > > i_mapping,
> > > ?? ?????? adev_to_drm(adev)-
> > > > vma_offset_manager,
> > > - ?????? adev->need_swiotlb,
> > > - ?????? dma_addressing_limited(adev-
> > > >dev));
> > > + ?????? (struct ttm_device_init_flags){
> > > + ?????? .use_dma_alloc = adev-
> > > > need_swiotlb,
> > > + ?????? .use_dma32 =
> > > dma_addressing_limited(adev->dev)
> > > + ?????? });
> > > ?? if (r) {
> > > ?? DRM_ERROR("failed initializing buffer o...
2024 Oct 05
1
[PATCH v2 1/2] drm/ttm: Change ttm_device_init to use a struct instead of multiple bools
...gt; > i_mapping,
> > > > ?? ?????? adev_to_drm(adev)-
> > > > > vma_offset_manager,
> > > > - ?????? adev->need_swiotlb,
> > > > - ?????? dma_addressing_limited(adev-
> > > > >dev));
> > > > + ?????? (struct ttm_device_init_flags){
> > > > + ?????? .use_dma_alloc = adev-
> > > > > need_swiotlb,
> > > > + ?????? .use_dma32 =
> > > > dma_addressing_limited(adev->dev)
> > > > + ?????? });
I can't say I like declaring the ttm_device_init_flags as pa...
2024 Oct 02
2
[PATCH v2 0/2] drm/ttm: Add an option to report graphics memory OOM
Some graphics APIs differentiate between out-of-graphics-memory and
out-of-host-memory (system memory). Add a device init flag to
have -ENOSPC propagated from the resource managers instead of being
converted to -ENOMEM, to aid driver stacks in determining what
error code to return or whether corrective action can be taken at
the driver level.
The first patch deals with a ttm_device_init()