/* * This header provides macros for MAXIM MAX77620 device bindings. * * Copyright (c) 2016, NVIDIA Corporation. * Author: Laxman Dewangan */ #ifndef _DT_BINDINGS_MFD_MAX77620_H #define _DT_BINDINGS_MFD_MAX77620_H /* MAX77620 interrupts */ #define MAX77620_IRQ_TOP_GLBL 0 /* Low-Battery */ #define MAX77620_IRQ_TOP_SD 1 /* SD power fail */ #define MAX77620_IRQ_TOP_LDO 2 /* LDO power fail */ #define MAX77620_IRQ_TOP_GPIO 3 /* GPIO internal int to MAX77620 */ #define MAX77620_IRQ_TOP_RTC 4 /* RTC */ #define MAX77620_IRQ_TOP_32K 5 /* 32kHz oscillator */ #define MAX77620_IRQ_TOP_ONOFF 6 /* ON/OFF oscillator */ #define MAX77620_IRQ_LBT_MBATLOW 7 /* Thermal alarm status, > 120C */ #define MAX77620_IRQ_LBT_TJALRM1 8 /* Thermal alarm status, > 120C */ #define MAX77620_IRQ_LBT_TJALRM2 9 /* Thermal alarm status, > 140C */ /* FPS event source */ #define MAX77620_FPS_EVENT_SRC_EN0 0 #define MAX77620_FPS_EVENT_SRC_EN1 1 #define MAX77620_FPS_EVENT_SRC_SW 2 /* Device state when FPS event LOW */ #define MAX77620_FPS_INACTIVE_STATE_SLEEP 0 #define MAX77620_FPS_INACTIVE_STATE_LOW_POWER 1 /* FPS source */ #define MAX77620_FPS_SRC_0 0 #define MAX77620_FPS_SRC_1 1 #define MAX77620_FPS_SRC_2 2 #define MAX77620_FPS_SRC_NONE 3 #define MAX77620_FPS_SRC_DEF 4 #endif value='packet-loop-back'>packet-loop-back net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/include/dt-bindings/clock/qcom,mmcc-msm8960.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-01 12:27:05 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-01 12:27:05 -0800
commit4759d386d55fef452d692bf101167914437e848e (patch)
treee7109c192ec589fcea2a98f9702aa3c0e4009581 /include/dt-bindings/clock/qcom,mmcc-msm8960.h
parent238d1d0f79f619d75c2cc741d6770fb0986aef24 (diff)
parent1db175428ee374489448361213e9c3b749d14900 (diff)
Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull DAX updates from Dan Williams: "The completion of Jan's DAX work for 4.10. As I mentioned in the libnvdimm-for-4.10 pull request, these are some final fixes for the DAX dirty-cacheline-tracking invalidation work that was merged through the -mm, ext4, and xfs trees in -rc1. These patches were prepared prior to the merge window, but we waited for 4.10-rc1 to have a stable merge base after all the prerequisites were merged. Quoting Jan on the overall changes in these patches: "So I'd like all these 6 patches to go for rc2. The first three patches fix invalidation of exceptional DAX entries (a bug which is there for a long time) - without these patches data loss can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks
Diffstat (limited to 'include/dt-bindings/clock/qcom,mmcc-msm8960.h')