diff options
author | Tom Warren <twarren@nvidia.com> | 2019-11-12 13:17:37 -0700 |
---|---|---|
committer | Tom Warren <twarren@nvidia.com> | 2020-04-02 14:30:02 -0700 |
commit | 3c8cf240322e76eebbb31593c96f0754092df91f (patch) | |
tree | e4b31b8a70b0bc995fd90e31195cb50f2b0c9a39 /drivers/memory | |
parent | a482f32992230d8bdae2caa72056ab7d9208d5f0 (diff) |
qspi: t210: Fix claim_bus's use of the wrong bus/device
claim_bus() is passed a udevice *dev, which is the bus device's parent.
In this driver, claim_bus assumed it was the bus, which caused the
'priv' info pointer to be wrong, and periph_id was incorrect. This in
turn caused the periph clock call to assign the wrong clock (PLLM
instead of PLLP0), which caused a kernel warning. I only saw the 'bad'
periph_id when enabling DEBUG due to an assert. Not sure how QSPI was
working w/this errant clock, but it was moot as QSPI wasn't active
unless you probed it, and that wasn't happening until I posted a patch
to enable env save to QSPI for Nano (coming soon).
Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'drivers/memory')
0 files changed, 0 insertions, 0 deletions