summaryrefslogtreecommitdiff
path: root/drivers/crypto
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-02-08 13:13:26 (GMT)
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-26 23:32:11 (GMT)
commit0dd5235f51fb0eb0b8cef3fed35be39b8a06d7bd (patch)
treec828429698c28367a5f5804ce1c3f0972af83ff4 /drivers/crypto
parentc3faac4a74c2126e2b68f39d6e8791e88b5f7dbe (diff)
downloadlinux-fsl-qoriq-0dd5235f51fb0eb0b8cef3fed35be39b8a06d7bd.tar.xz
mtd: harmonize mtd_point interface implementation
Some MTD drivers return -EINVAL if the 'phys' parameter is not NULL, trying to convey that they cannot return the physical address. However, this is not very logical because they still can return the virtual address ('virt'). But some drivers (lpddr) just ignore the 'phys' parameter instead, which is a more logical thing to do. Let's harmonize this and: 1. Always initialize 'virt' and 'phys' to 'NULL' in 'mtd_point()'. 2. Do not return an error if the physical address cannot be found. So as a result, all drivers will set 'phys' to 'NULL' if it is not supported. None of the 'mtd_point()' users use 'phys' anyway, so this should not break anything. I guess we could also just delete this parameter later. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/crypto')
0 files changed, 0 insertions, 0 deletions