summaryrefslogtreecommitdiffstats
path: root/drivers/mtd
diff options
context:
space:
mode:
authorBrian Norris <computersforpeace@gmail.com>2015-03-27 10:29:49 -0700
committerBrian Norris <computersforpeace@gmail.com>2015-04-05 18:56:21 -0700
commit8ff16cf77ce314c20d7bd57c788f5b7719b450e1 (patch)
treeaf87664493601e40ac34d7f594dc3db6c7b1b3e0 /drivers/mtd
parent2a6a28e7922c07c116ba8f2aa3682c03ef8be678 (diff)
downloadlinux-8ff16cf77ce314c20d7bd57c788f5b7719b450e1.tar.gz
linux-8ff16cf77ce314c20d7bd57c788f5b7719b450e1.tar.bz2
linux-8ff16cf77ce314c20d7bd57c788f5b7719b450e1.zip
Documentation: devicetree: m25p80: add "nor-jedec" binding
Almost all flash that are "compatible" with m25p80 support the JEDEC READ ID opcode (0x9F), and in fact, that is often the only thing that is used to differentiate them. Let's add a compatible string that represents this lowest common denominator of compatibility. Device trees can still specify manufacturer/device names in addition, but (until some reason is found to differentiate between them through device tree) software will likely want to bind just against the generic name, and avoid unnecessarily growing its device ID binding tables. This is related to the work of commit a5b7616c55e1 ("mtd: m25p80,spi-nor: Fix module aliases for m25p80"), which showed that maintaining these device tables as stable device-tree/modalias binding tables is not a worthwhile burden for mostly-comptatible flash. At the same time, let's update the binding doc to point to the m25p_ids[] ID list instead of spi_nor_ids[]. The former can be used for device tree bindings, but the latter cannot. In the future, we should pare down the m25p_ids[] list to only those IDs which are actually used in device trees. Signed-off-by: Brian Norris <computersforpeace@gmail.com> Cc: Rafał Miłecki <zajec5@gmail.com> Reviewed-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'drivers/mtd')
0 files changed, 0 insertions, 0 deletions