summaryrefslogtreecommitdiffstats
path: root/drivers/nvmem
diff options
context:
space:
mode:
authorHoratiu Vultur <horatiu.vultur@microchip.com>2022-09-28 21:51:12 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-11-10 18:45:01 +0100
commit1aeb122d214b92474c86fde00a03d6e2d69381b5 (patch)
tree7f85dc6b96e328e967728baae5ebcb0b3810b4f7 /drivers/nvmem
parentbinder: validate alloc->mm in ->mmap() handler (diff)
downloadlinux-1aeb122d214b92474c86fde00a03d6e2d69381b5.tar.xz
linux-1aeb122d214b92474c86fde00a03d6e2d69381b5.zip
nvmem: lan9662-otp: Fix compatible string
The device tree bindings for lan9662-otp expects the compatible string to be one of following compatible strings: microchip,lan9662-otpc microchip,lan9668-otpc The problem is that the lan9662-otp driver contains the microchip,lan9662-otp compatible string instead of microchip,lan9662-otpc. Fix this by updating the compatible string in the driver. Fixes: 9e8f208ad5229d ("nvmem: lan9662-otp: add support") Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com> Link: https://lore.kernel.org/r/20220928195112.630351-1-horatiu.vultur@microchip.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/nvmem')
-rw-r--r--drivers/nvmem/lan9662-otpc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/nvmem/lan9662-otpc.c b/drivers/nvmem/lan9662-otpc.c
index f6732fd216d8..377bf34c2946 100644
--- a/drivers/nvmem/lan9662-otpc.c
+++ b/drivers/nvmem/lan9662-otpc.c
@@ -203,7 +203,7 @@ static int lan9662_otp_probe(struct platform_device *pdev)
}
static const struct of_device_id lan9662_otp_match[] = {
- { .compatible = "microchip,lan9662-otp", },
+ { .compatible = "microchip,lan9662-otpc", },
{ },
};
MODULE_DEVICE_TABLE(of, lan9662_otp_match);