mszyprow has joined #linux-exynos
krzk_ has joined #linux-exynos
decay has joined #linux-exynos
decay_ has quit [*.net *.split]
krzk has quit [*.net *.split]
dlezcano has joined #linux-exynos
kxkamil has joined #linux-exynos
PabloPL has joined #linux-exynos
PabloPL has quit [Client Quit]
PabloPL has joined #linux-exynos
PabloPL has quit [Client Quit]
PabloPL has joined #linux-exynos
PabloPL has quit [Quit: PabloPL]
dlezcano has quit [Quit: ZNC - http://znc.in]
dlezcano has joined #linux-exynos
dlezcano has quit [Client Quit]
dlezcano has joined #linux-exynos
dlezcano has quit [Client Quit]
dlezcano has joined #linux-exynos
dlezcano has quit [Client Quit]
dlezcano has joined #linux-exynos
dlezcano has quit [Client Quit]
dlezcano has joined #linux-exynos
PabloPL has joined #linux-exynos
<PabloPL> "Samsung Exynos7 Espresso board" (from exynos7-espresso.dts) is based on which exynos7 cpu?
<ahajda> Probably on some revision of 7420: https://lists.denx.de/pipermail/u-boot/2016-April/251646.html
<PabloPL> ahajda: So if we would like to add support for some other exynos7 soc, we should at first rename it from exynos7 to exynos7420?
<PabloPL> ahajda: I've looked at some dts of 7580 based phones and they're different
<PabloPL> ahajda: thanks for that uboot link. Maybe it could be used to create something like we have for s5pv210 :)
<krzk_> PabloPL: The Exynos7 contributors never explained in detailed way which SoC is that but I remember talks (cannot find email now) and they said it is not Exynos7420. It is Exynos7 :)
<ahajda> I guess you can ignore exynos7 and just start using exynos7580, unless you want to clean-up this :)
<krzk_> but also according to their explanation - very close to 7420
<ahajda> that's why I said 'probably' and 'revision' :)
<krzk_> so as of now, Exynos7 is not treated like family but as specific SoC
<ahajda> If I remember correctly it differs from 7420 present in Galaxy phones
<krzk_> ahajda: yeah, that would make sense
<PabloPL> ok, so for other exynos7* we need to ignore this and start from "scratch"
<krzk_> PabloPL: what do you mean scratch?
<PabloPL> krzk_: create for example in my case base exynos7580.dtsi (not using exynos7.dtsi)
<krzk_> Some things could be re-used, maybe parts of pinctrl/clock... dts as well
<krzk_> ah, depends, I did not check about 7580 differences
<krzk_> if it shares a lot with 7420, then common dtsi makes sense
<krzk_> if it does not share too much, then probably from scratch... it is the same as with exynos4 and exynos5
<PabloPL> krzk_: Yes, i mean that they could be similar, but one should not depend on another (like i though at first sight - though that it's base for all exynos7 soc)
mszyprow has quit [Ping timeout: 272 seconds]
PabloPL has quit [Quit: PabloPL]
genii has joined #linux-exynos
kxkamil has quit [Quit: Leaving]
Putti has quit [Read error: Connection reset by peer]
Putti has joined #linux-exynos
putti_ has joined #linux-exynos
Putti has quit [Remote host closed the connection]
putti_ is now known as Putti
mszyprow|home has joined #linux-exynos
LiquidAcid has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 246 seconds]
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 272 seconds]
mszyprow|home has joined #linux-exynos
LiquidAcid has quit [Quit: Leaving]
LiquidAcid has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 244 seconds]
mszyprow|home has joined #linux-exynos
PabloPL has joined #linux-exynos
<PabloPL> Could someone with access to exynos7580 manual check, what value is for reset stat bit in EXYNOS5_RST_STAT_REG_OFFSET (0x0404) ? If it's 23, then i could reuse what was added for exynos7 (other values in s3c2410_wdt_variant looks identical)
PabloPL has quit [Quit: Wychodzi]
mszyprow|home has quit [Ping timeout: 268 seconds]
adjtm_ has joined #linux-exynos
adjtm has quit [Ping timeout: 272 seconds]
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 246 seconds]