lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Jan 2018 18:43:21 -0600 From: Suman Anna <s-anna@...com> To: Tony Lindgren <tony@...mide.com> CC: Philipp Zabel <p.zabel@...gutronix.de>, Philipp Zabel <philipp.zabel@...il.com>, Paul Parsons <lost.distance@...oo.com>, <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, <linux-omap@...r.kernel.org>, Dave Gerlach <d-gerlach@...com>, Mark Rutland <mark.rutland@....com>, Nishant Menon <nm@...com>, Rob Herring <robh+dt@...nel.org>, Tero Kristo <t-kristo@...com> Subject: Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver On 01/19/2018 05:49 PM, Tony Lindgren wrote: > * Suman Anna <s-anna@...com> [180119 23:30]: >> On 01/19/2018 03:33 PM, Tony Lindgren wrote: >>> OK let's do some tests on that, I'll take a look at doing a dts >>> file over next few weeks. >> >> You can look up the patches folder in the above repo, there are some >> example nodes there already, they are rather straight-forward. > > Just for reference, here's what I played with but keep getting > -EPROBE_DEFER somewhere during init. Hmm, What's the baseline branch you are using - mainline, linux-next or your for-next? > > Regards, > > Tony > > prm: prm@...0 { > ... > ranges = <0 0x6000 0x3000>; > > prm_dsp: prm@400 { > compatible = "simple-bus"; > #address-cells = <1>; > #size-cells = <1>; > ranges = <0 0x400 0x100>; > > dsp_rstctrl: rstctrl@10 { > compatible = "ti,rstctrl"; > reg = <0x10 0x4>; > #reset-cells = <1>; > }; > }; > ... > }; > > target-module@...66000 { > compatible = "ti,sysc-omap2", "ti,sysc"; > ti,hwmods = "mmu_dsp"; > reg = <0x4a066000 0x4>, > <0x4a066010 0x4>, > <0x4a066014 0x4>; > reg-names = "rev", "sysc", "syss"; > ti,sysc-mask = <(SYSC_OMAP2_CLOCKACTIVITY | > SYSC_OMAP2_SOFTRESET | > SYSC_OMAP2_AUTOIDLE)>; > ti,sysc-sidle = <SYSC_IDLE_FORCE>, > <SYSC_IDLE_NO>, > <SYSC_IDLE_SMART>; > clocks = <&tesla_clkctrl OMAP4_DSP_CLKCTRL 0>; > clock-names = "fck"; > resets = <&dsp_rstctrl 1>, > <&dsp_rstctrl 0>; > reset-names = "rst2", "rst1"; We definitely do not want the two resets here for sure, as the rst2 belongs to the dsp core (I believe it would be a sibling node to mmu_dsp here), and cannot be released from reset without programming the MMU and loading the code. regards Suman > #address-cells = <1>; > #size-cells = <1>; > ranges = <0 0x4a066000 0x1000>; > > mmu_dsp: mmu@0 { > compatible = "ti,omap4-iommu"; > reg = <0 0x100>; > interrupts = <GIC_SPI 28 IRQ_TYPE_LEVEL_HIGH>; > #iommu-cells = <0>; > }; > }; >
Powered by blists - more mailing lists