iommu: Regulate EINVAL in ->attach_dev callback functions
authorNicolin Chen <nicolinc@nvidia.com>
Mon, 17 Oct 2022 23:02:13 +0000 (16:02 -0700)
committerJason Gunthorpe <jgg@nvidia.com>
Tue, 1 Nov 2022 17:39:59 +0000 (14:39 -0300)
commitbd7ebb7719356d750b1b4d671535922bae43fb3b
tree8867784273e8e5319862a5a67a9a6f57f8f7d530
parent00208852d351ca6e4a8b9ff0c5376fa3a8ed8eaa
iommu: Regulate EINVAL in ->attach_dev callback functions

Following the new rules in include/linux/iommu.h kdocs, EINVAL now can be
used to indicate that domain and device are incompatible by a caller that
treats it as a soft failure and tries attaching to another domain.

On the other hand, there are ->attach_dev callback functions returning it
for obvious device-specific errors. They will result in some inefficiency
in the caller handling routine.

Update these places to corresponding errnos following the new rules.

Link: https://lore.kernel.org/r/5924c03bea637f05feb2a20d624bae086b555ec5.1666042872.git.nicolinc@nvidia.com
Reviewed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
drivers/iommu/fsl_pamu.c
drivers/iommu/fsl_pamu_domain.c
drivers/iommu/intel/pasid.c
drivers/iommu/mtk_iommu.c
drivers/iommu/omap-iommu.c
drivers/iommu/virtio-iommu.c