From: Eric Anholt <eric@anholt.net>
To: Dave Emett <david.emett@broadcom.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Thomas Spurden <thomas.spurden@broadcom.com>
Subject: Re: [PATCH v4 2/2] drm/v3d: Add support for V3D v4.2.
Date: Fri, 08 Mar 2019 15:12:22 -0800 [thread overview]
Message-ID: <87k1h99d0p.fsf@anholt.net> (raw)
In-Reply-To: <CAApk1dVbYaxBi7LVNgvVBabCZaWp7=yJ5YDMq3ozz4-peZnaGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Dave Emett <david.emett@broadcom.com> writes:
> On Fri, 8 Mar 2019 at 17:43, Eric Anholt <eric@anholt.net> wrote:
>>
>> No compatible string for it yet, just the version-dependent changes.
>> They've now tied the hub and the core interrupt lines into a single
>> interrupt line coming out of the block. It also turns out I made a
>> mistake in modeling the V3D v3.3 and v4.1 bridge as a part of V3D
>> itself -- the bridge is going away in favor of an external reset
>> controller in a larger HW module.
>>
>> v2: Use consistent checks for whether we're on 4.2, and fix a leak in
>> an error path.
>> v3: Use more general means of determining if the current 4.2 changes
>> are in place, as apparently other platforms may switch back (noted
>> by Dave). Update the binding doc.
>> v4: Improve error handling for IRQ init.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
>
> Reviewed-by: Dave Emett <david.emett@broadcom.com>
Pushed to drm-misc-next. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-03-08 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 17:43 [PATCH v4 1/2] drm/v3d: Handle errors from IRQ setup Eric Anholt
2019-03-08 17:43 ` [PATCH v4 2/2] drm/v3d: Add support for V3D v4.2 Eric Anholt
2019-03-08 18:18 ` Dave Emett
2019-03-08 23:12 ` Eric Anholt [this message]
2019-03-08 18:22 ` [PATCH v4 1/2] drm/v3d: Handle errors from IRQ setup Dave Emett
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=87k1h99d0p.fsf@anholt.net \
--to=eric@anholt.net \
--cc=david.emett@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.spurden@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox