summaryrefslogtreecommitdiffstats
path: root/fs/d_path.c
diff options
context:
space:
mode:
authorNiklas Cassel <niklas.cassel@linaro.org>2019-04-25 14:34:01 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-08-06 19:08:02 +0200
commit41979b6c0baae98abc4ed601ee6c03fd8850b9c2 (patch)
tree6cbc7d9ed5c65e9c28556dd647c57a7fc121e25f /fs/d_path.c
parent004e0c5d77e8ad6d5adcce358209ce061d7eb5ef (diff)
downloadlinux-stable-41979b6c0baae98abc4ed601ee6c03fd8850b9c2.tar.gz
linux-stable-41979b6c0baae98abc4ed601ee6c03fd8850b9c2.tar.bz2
linux-stable-41979b6c0baae98abc4ed601ee6c03fd8850b9c2.zip
arm64: dts: qcom: qcs404-evb: fix l3 min voltage
[ Upstream commit 887b528c958f40b064d53edd0bfa9fea3a69eccd ] The current l3 min voltage level is not supported by the regulator (the voltage is not a multiple of the regulator step size), so a driver requesting this exact voltage would fail, see discussion in: https://patchwork.kernel.org/comment/22461199/ It was agreed upon to set a min voltage level that is a multiple of the regulator step size. There was actually a patch sent that did this: https://patchwork.kernel.org/patch/10819313/ However, the commit 331ab98f8c4a ("arm64: dts: qcom: qcs404: Fix voltages l3") that was applied is not identical to that patch. Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Andy Gross <agross@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/d_path.c')
0 files changed, 0 insertions, 0 deletions