From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
"Merlijn Wajer" <merlijn@wizzup.org>,
"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>,
"Philipp Rossak" <embed3d@gmail.com>,
"moaz korena" <moaz@korena.xyz>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Filip Matijević" <filip.matijevic.pz@gmail.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
kernel@pyra-handheld.com,
"Discussions about the Letux Kernel"
<letux-kernel@openphoenux.org>,
maemo-leste@lists.dyne.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Lay common foundation to make PVR/SGX work without hacks on OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5
Date: Wed, 21 Aug 2019 04:38:50 -0700 [thread overview]
Message-ID: <20190821113850.GP52127@atomide.com> (raw)
In-Reply-To: <CAHCN7xJH6ZjksNZ2cyb1rN_TiF-0GKAtW9KD1kv1-JE+gqLgEA@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [190819 19:26]:
> On Sat, Aug 17, 2019 at 2:03 AM Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Adam Ford <aford173@gmail.com> [190816 23:02]:
> > > On Wed, Aug 14, 2019 at 8:16 AM Tony Lindgren <tony@atomide.com> wrote:
> > > > Well I just posted some sgx interconnect target module patches. We might
> > > > still have them in v5.4 assuming people manage to review and test them.
> > >
> > > Nikolaus,
> > >
> > > I tested Tony's change and I can confirm that I can read the value
> > > when enabled. Should I apply his patches to your branch before I
> > > test, or is it go too to go as-is? I've got an AM3517, OMAP35 and a
> > > DM3730. I am not sure if the AM3517 is even on the radar, but it has
> > > an sgx530 as well.
> >
> > My estimate is am3517 is wired the same way as omap34xx with a 60%
> > chance, then 30% chance it's wired the same way as omap36xx, and then
> > 10% chance for similar wiring to am335x.. So hopefully that leaves 0%
> > chance for yet something different for it's wiring :)
>
> Based on [1], I went under the assumption it was wired like the
> omap34xx. I applied your omap34 patches to the am3517.dtsi, and I was
> able to get the same response as I did for the omap3530. Do you want
> me to post the patches to the mailing list, or do you want to do it?
OK great, yeah please post patches :)
Thanks,
TOny
next prev parent reply other threads:[~2019-08-21 11:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180108214032.GW3872@atomide.com>
[not found] ` <4d99c1ae-7752-949b-7e88-bc8f1dc594a2@wizzup.org>
[not found] ` <0C51EC59-9CDC-4196-ACF9-24596C9E61B6@goldelico.com>
[not found] ` <FA4520D5-62CB-446D-975C-A1C7B9251517@goldelico.com>
[not found] ` <20190212205132.GO5720@atomide.com>
[not found] ` <0b00ce0a-969f-e638-8247-c2da96cf7ce6@gmail.com>
[not found] ` <20190213004143.GP5720@atomide.com>
[not found] ` <480AB632-A544-41E7-95A4-DC354AEBB71A@goldelico.com>
[not found] ` <CAKpie0SigGGsQxSU+X-Mz5boy-Xx=3wRNOcrf+F=ehFr3RBi7Q@mail.gmail.com>
[not found] ` <092210C3-05DE-4AFB-986F-81BD8F990B67@goldelico.com>
[not found] ` <CAKpie0RXM1UC33YFeFy-kAxfGhYGNkw4vUgNTThf-ZCAhPTVXw@mail.gmail.com>
[not found] ` <BE23C1E4-2877-49FA-B230-F9C10691B805@goldelico.com>
[not found] ` <CAKpie0TSo-8gmDm9_Zw4Sd+kjVVEomp8yA9Vu8qY2U2AcrQc=w@mail.gmail.com>
[not found] ` <8A069D96-C65F-43F5-8F54-20019CFB1A8D@goldelico.com>
[not found] ` <d0cbfaaf-813e-8803-f90b-931a38396750@wizzup.org>
[not found] ` <3A03F F16-C203-43ED-AEEF-0260F6B3331A@goldelico.com>
[not found] ` <3b0a5e78-c4c2-1963-bac7-b49496a1e9b9@wizzup.org>
[not found] ` <1F942AAB-1648-46C0-ADD5-90F6898778BE@goldelico.com>
[not found] ` <84cac9b8-0eff-33f8-464d-4f8045d7db19@wizzup.org>
2019-08-14 8:56 ` Lay common foundation to make PVR/SGX work without hacks on OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5 H. Nikolaus Schaller
2019-08-14 8:56 ` H. Nikolaus Schaller
2019-08-14 9:47 ` Tony Lindgren
2019-08-14 10:33 ` H. Nikolaus Schaller
2019-08-14 13:16 ` Tony Lindgren
2019-08-16 23:01 ` Adam Ford
2019-08-17 7:03 ` Tony Lindgren
2019-08-19 19:25 ` Adam Ford
2019-08-21 11:38 ` Tony Lindgren [this message]
2019-08-17 9:01 ` H. Nikolaus Schaller
2019-08-19 19:43 ` Adam Ford
2019-08-20 6:48 ` H. Nikolaus Schaller
2019-08-20 6:48 ` H. Nikolaus Schaller
2019-08-20 7:09 ` Merlijn Wajer
[not found] ` <C3A56737-6187-4B31-8697-3A02DD164429@goldelico.com>
2019-10-07 15:52 ` Tony Lindgren
2019-10-07 15:56 ` H. Nikolaus Schaller
2019-10-07 19:18 ` Tero Kristo
2019-10-07 19:24 ` H. Nikolaus Schaller
2019-10-08 8:00 ` Tero Kristo
2019-10-08 8:00 ` Tero Kristo
2019-10-08 13:49 ` Tony Lindgren
2019-10-08 20:15 ` H. Nikolaus Schaller
2019-10-09 12:53 ` H. Nikolaus Schaller
2019-10-09 13:55 ` Tero Kristo
2019-10-09 14:23 ` H. Nikolaus Schaller
2019-10-09 14:23 ` H. Nikolaus Schaller
2019-10-09 16:34 ` Tero Kristo
2019-10-09 19:53 ` H. Nikolaus Schaller
2019-10-09 19:53 ` H. Nikolaus Schaller
2019-10-12 13:09 ` [Letux-kernel] " H. Nikolaus Schaller
2019-10-12 13:09 ` H. Nikolaus Schaller
2019-10-14 16:11 ` H. Nikolaus Schaller
2019-10-14 16:11 ` H. Nikolaus Schaller
2019-10-16 23:03 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190821113850.GP52127@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=embed3d@gmail.com \
--cc=filip.matijevic.pz@gmail.com \
--cc=hns@goldelico.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=maemo-leste@lists.dyne.org \
--cc=merlijn@wizzup.org \
--cc=moaz@korena.xyz \
--cc=pawel.mikolaj.chmiel@gmail.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.