Re: External data abort on ipq6018 gpio # 20 ~ offset 0x14000 any ideas ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2022-01-01 21:17, Bryan O'Donoghue wrote:
On 31/12/2021 21:18, Bjorn Andersson wrote:
Unfortunately I don't know how to determine the list of protected GPIOs,
other than trial and error.

But once you have the list, you can use "gpio-reserved-ranges" (a series
of offset, count pairs) in the TLMM DT node to mark off these gpios as
reserved.

Ah nice, worked first time.

gpio-reserved-ranges = <20 4>;


You want to protect only one GPIO right? I understand that it should be just <20 1>. Isn't the case?

You are using a CP01-C4 variant(#define CPU_IPQ6005 453, machid 0x8030003). In this variant alone, GPIO20 is protected by TZ for some of its operation since there is no PMIC. In other variants of IPQ6018, you shouldn't be seeing this issue.


Well I guess its good to know there's no more esoteric explanation
than "trustzone made it explode" - it only seems to be the one GPIO
too, quite what use there is for TZ in this GPIO

PINGROUP(20, pwm20, atest_char2, _, _, _, _, _, _, _)

is anybody's guess.

Good enough for my purposes.

Thanks !

---
bod

--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux