On Mon, Nov 17, 2014 at 7:19 AM, <arul.ramasamy@xxxxxxxxxx> wrote: > From: Arul Ramasamy <Arul.Ramasamy@xxxxxxxxxx> > > The Pistachio SOC from Imagination Technologies includes a eFuse Controller > which exposes the status of 128 EFUSE bits to the external world. > > Signed-off-by: Arul Ramasamy <Arul.Ramasamy@xxxxxxxxxx> > Signed-off-by: Jude Abraham <Jude.Abraham@xxxxxxxxxx> > Signed-off-by: Naidu Tellapati <Naidu.Tellapati@xxxxxxxxxx> > drivers/soc/Kconfig | 1 + > drivers/soc/Makefile | 1 + > drivers/soc/pistachio/Makefile | 1 + > drivers/soc/pistachio/fuse/Kconfig | 9 ++ > drivers/soc/pistachio/fuse/Makefile | 1 + > drivers/soc/pistachio/fuse/img-efuse.c | 184 +++++++++++++++++++++++++++++++++ > include/soc/pistachio/img-efuse.h | 17 +++ > 7 files changed, 214 insertions(+) > create mode 100644 drivers/soc/pistachio/Makefile > create mode 100644 drivers/soc/pistachio/fuse/Kconfig > create mode 100644 drivers/soc/pistachio/fuse/Makefile > create mode 100644 drivers/soc/pistachio/fuse/img-efuse.c > create mode 100644 include/soc/pistachio/img-efuse.h Is this IP present on other ImgTec SoCs? Perhaps it makes more sense to create drivers/soc/img/ instead of drivers/soc/pistachio/? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
