Since AMLogic's GPIOLIB does not support standard framework yet,
of_get_named_gpio_flags is replaced to use AMLogic's own framework such that
GPIO will be obtained from wrapper function.
FIXME: This is not a right way to support for gpio and pinctrl.
Change-Id: I29b5a3bc99bbfa7b299c575b08e10fea81935cef
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Since ODROID-C does not PMU, it won't stop or off completely. Hence this
reboot condition will reach to bootloader and halt the system.
Change-Id: I6bb8c5628bfbf0f9c120062fe7cb207aeb2aac2c
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
In order to assign a boot media to SDHC block between SDCARD or eMMC,
different two device tree have to be maintained. But this is risky to
maintain. Hence add both properties of SDCARD and eMMC to each contoller, SDHC
and SDIO, remove one of them in U-boot. Finally Linux kernel will have proper
device tree with corresponding to boot deivce.
Change-Id: I607575123f81e85d93c0c2613738e11f53892731
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Since ODROIDC does not have PMU for voltage scaling, only required to
scale the CPU frequencies.
Change-Id: I6e49d7b00fb057776e97fafc3a1dc6daa8494e1e
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
drivers/mtd/nand/nand_base.c:2863:12:
error: ‘nand_flash_detect_onfi’ defined but not used [-Werror=unused-function]
cc1: all warnings being treated as errors
Change-Id: I66511666e9dc561ae8adc06d73aa21b3856d3a37
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
This patch disables WiFi modules and removes from build.
Change-Id: Id17f18fe59122c7f676cf91c647ec1af285ff107
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
This reverts commit 74552b8f39694252758a0bed425386a9592fdd46.
Change-Id: I4c1b7b4c0b3155e950742ab7a552843e9deda731
Signed-off-by: Dongjin Kim <tobetter@gmail.com>
Since MESON8B has single SDHC and SDIO block, 'meson8b_odroidc.dtd' is to boot by sdcard
and 'meson8b_odroidc_emmc.dtd' by eMMC.
Change-Id: I5550197122c023d50665a3bcfc740567b99420f4
commit da87ca4d4c upstream.
Since commit 7787380336 "net_dma: mark broken" we no longer pin dma
engines active for the network-receive-offload use case. As a result
the ->free_chan_resources() that occurs after the driver self test no
longer has a NET_DMA induced ->alloc_chan_resources() to back it up. A
late firing irq can lead to ksoftirqd spinning indefinitely due to the
tasklet_disable() performed by ->free_chan_resources(). Only
->alloc_chan_resources() can clear this condition in affected kernels.
This problem has been present since commit 3e037454bc "I/OAT: Add
support for MSI and MSI-X" in 2.6.24, but is now exposed. Given the
NET_DMA use case is deprecated we can revisit moving the driver to use
threaded irqs. For now, just tear down the irq and tasklet properly by:
1/ Disable the irq from triggering the tasklet
2/ Disable the irq from re-arming
3/ Flush inflight interrupts
4/ Flush the timer
5/ Flush inflight tasklets
References:
https://lkml.org/lkml/2014/1/27/282https://lkml.org/lkml/2014/2/19/672
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>
Reported-by: Mike Galbraith <bitbucket@online.de>
Reported-by: Stanislav Fomichev <stfomichev@yandex-team.ru>
Tested-by: Mike Galbraith <bitbucket@online.de>
Tested-by: Stanislav Fomichev <stfomichev@yandex-team.ru>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 9f050c7f97 upstream.
Print the supported functions mask in addition to
the version. This is useful in debugging PX
problems since we can see what functions are available.
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 1acacc0784 upstream.
dm_pool_close_thin_device() must be called if dm_set_target_max_io_len()
fails in thin_ctr(). Otherwise __pool_destroy() will fail because the
pool will still have an open thin device:
device-mapper: thin metadata: attempt to close pmd when 1 device(s) are still open
device-mapper: thin: __pool_destroy: dm_pool_metadata_close() failed.
Also, must establish error code if failing thin_ctr() because the pool
is in fail_io mode.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 4d1662a30d upstream.
Commit 905e51b ("dm thin: commit outstanding data every second")
introduced a periodic commit. This commit occurs regardless of whether
any thin devices have made changes.
Fix the periodic commit to check if any of a pool's thin devices have
changed using dm_pool_changed_this_transaction().
Reported-by: Alexander Larsson <alexl@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit a1989b3300 upstream.
An invalid ioctl will never be valid, irrespective of whether multipath
has active paths or not. So for invalid ioctls we do not have to wait
for multipath to activate any paths, but can rather return an error
code immediately. This fix resolves numerous instances of:
udevd[]: worker [] unexpectedly returned with status 0x0100
that have been seen during testing.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
