The 'MPT' partition table is non-standard type which contains the partitions
at certain blocks on eMMC device to provide many partitions more than MBR
partition. When this partition table is discovered, standard partitions
such as MBR are ignored such that only the partitions from MPT are valid.
But there is a kernel crash bug when 'MPT' partition table is not exist.
This patch will check if 'MPT' partition is exist while checking its magic
number and proceed further more if it's valid.
Since Android needs to use 'MPT' partition, this cannot be simply eliminated.
Change-Id: Ic27fef3e28eab009affbb0f11a12472d58a373f6
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
After reduce the size of boot loader area to fit in 1MB, MPT partition table
can be fit at 2048 LBA and this partition table would be used by Android
for numerous partitions other than Linux based platforms.
Change-Id: Ic8b8defedb4103abf547bae7f533036904578b59
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Conflicts:
drivers/mmc/card/block.c
It has two main use cases:
1) Allow drivers to reset their hardware via a GPIO line in a standard fashion
as supplied by the reset framework.
This allows adhoc driver code requesting GPIOs etc to be replaced with a
single call to device_reset().
2) Allow hardware on discoverable busses to be rest via a GPIO line
without driver modifications.
Examples of the second use case include:
* SDIO wifi modules
* USB hub chips with a reset line
In this second use case the reset has to be done externally to the driver
managing the hardware since resetting the device from the driver's probe()
method will either do nothing (if the device needs to be reset before
ennumeration will work) or cause racy beahviour (when the device disappears
from the bus during probe()).
So, in addition to providing a gpio based reset controller implementation
it is also possible to reset devices at boot via a DT property or from
userspace on request via sysfs attributes.
Change-Id: I316f9e622d99cff7167b57e8fd5ff73a34dc2a81
Signed-off-by: Martin Fuzzey <mfuzzey@parkeon.com>
Signed-off-by: Kevin Kim <ckkim@hardkernel.com>
This patch adds support of vendor sub directories for dtb files.
Subdirectories can be specified in $(dts-dirs). Kbuild traverses over
all directories while building and installing dtb files. The directory
tree is also reflected in the install path.
Change-Id: Iab8d4cf4b76f7122892e87137fd0ec60565e1db0
Tested-by: Andrew Bresticker <abrestic@chromium.org>
Signed-off-by: Robert Richter <rrichter@cavium.com>
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
This adds the dtbs_install make target to arm64. The target has been
introduced already to arch/arm with the following commit:
f4d4ffc03e kbuild: dtbs_install: new make target
Implementation for arm64 is the same as for arm.
With 'dtbs_install' all config enabled dtb files are installed to
either the INSTALL_DTBS_PATH directory or the default location:
$INSTALL_PATH/dtbs/$KERNELRELEASE
Change-Id: I5605ea7d723e2a658f7d85177d1221b83d612bcb
Signed-off-by: Robert Richter <rrichter@cavium.com>
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
