Re: dma_declare_coherent_memory on main memory

2018-12-10 Thread Sascha Hauer
On Fri, Dec 07, 2018 at 04:34:32PM +0100, Christoph Hellwig wrote: > Hi all, > > the ARM imx27/31 ports and various sh boards use > dma_declare_coherent_memory on main memory taken from the memblock > allocator. > > Is there any good reason these couldn't be switched to CMA areas? > Getting rid o

Re: [RFC 4/4] drm: Add NVIDIA Tegra support

2012-04-12 Thread Sascha Hauer
On Wed, Apr 11, 2012 at 12:12:14PM -0600, Stephen Warren wrote: > On 04/11/2012 06:10 AM, Thierry Reding wrote: > > This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It > > currently has rudimentary GEM support and can run a console on the > > framebuffer as well as X using the xf86-v

Re: [PATCH] drm/rockchip: Refactor IOMMU initialisation

2022-04-08 Thread Sascha Hauer
On Tue, Apr 05, 2022 at 03:32:50PM +0100, Robin Murphy wrote: > Defer the IOMMU domain setup until after successfully binding > components, so we can figure out IOMMU support directly from the VOP > devices themselves, rather than manually inferring it from the DT (which > also fails to account for

Re: [PATCH v2 7/9] driver core: Set fw_devlink.strict=1 by default

2022-06-22 Thread Sascha Hauer
On Wed, Jun 01, 2022 at 12:07:03AM -0700, Saravana Kannan wrote: > Now that deferred_probe_timeout is non-zero by default, fw_devlink will > never permanently block the probing of devices. It'll try its best to > probe the devices in the right order and then finally let devices probe > even if thei

Re: [PATCH v2 7/9] driver core: Set fw_devlink.strict=1 by default

2022-06-22 Thread Sascha Hauer
On Wed, Jun 22, 2022 at 12:52:02PM +0200, Andy Shevchenko wrote: > On Wed, Jun 22, 2022 at 10:44 AM Linus Walleij > wrote: > > On Wed, Jun 22, 2022 at 9:48 AM Sascha Hauer wrote: > > ... > > > > This patch has the effect that console UART devices which have &qu

Re: [PATCH v1 1/2] driver core: fw_devlink: Allow firmware to mark devices as best effort

2022-06-22 Thread Sascha Hauer
ink.strict=1 by default"). > > Fixes: 71066545b48e ("driver core: Set fw_devlink.strict=1 by default") > Reported-by: Sascha Hauer > Reported-by: Peng Fan > Signed-off-by: Saravana Kannan > --- > drivers/base/core.c| 3 ++- > include/linux/fwnode.h | 4 >

Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1

2022-06-23 Thread sascha hauer
en make the decision on where it can probe without those > suppliers or defer its probe. > > Fixes: 71066545b48e ("driver core: Set fw_devlink.strict=1 by default") > Reported-by: Sascha Hauer > Reported-by: Peng Fan > Signed-off-by: Saravana Kannan > Tested-by: Pe

Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1

2022-06-23 Thread sascha hauer
On Thu, Jun 23, 2022 at 10:26:46AM -0700, Saravana Kannan wrote: > On Thu, Jun 23, 2022 at 3:05 AM sascha hauer wrote: > > > > On Thu, Jun 23, 2022 at 01:03:43AM -0700, Saravana Kannan wrote: > > > Commit 71066545b48e ("driver core: Set fw_devlink.strict=1 by defau

Re: CAAM: kernel BUG at drivers/crypto/caam/jr.c:230! (and dma-coherent query)

2021-03-03 Thread Sascha Hauer
On Wed, Mar 03, 2021 at 12:26:32PM +0200, Horia Geantă wrote: > Adding some people in the loop, maybe they could help in understanding > why lack of "dma-coherent" property for a HW-coherent device could lead to > unexpected / strange side effects. > > On 3/1/2021 5: