Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1576670
| From | Marc Zyngier <marc.zyngier@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit |
| Date | 2017-02-08 17:00 +0100 |
| Message-ID | <t8CP0-2b0-21@gated-at.bofh.it> (permalink) |
| References | <t8oM1-1D5-3@gated-at.bofh.it> <t8zxM-h3-23@gated-at.bofh.it> <t8AtR-Rq-51@gated-at.bofh.it> <t8ADw-UD-15@gated-at.bofh.it> <t8ClX-20B-7@gated-at.bofh.it> |
| Organization | ARM Ltd |
On Wed, Feb 08 2017 at 2:09:12 pm GMT, Timur Tabi <timur@codeaurora.org> wrote: > Mark Rutland wrote: > >>> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2 >>> will have this fixed. We intend to revert these fixes after Falkor >>> V1 SOCs are no longer supported. >> >> Supported by whom? > > Qualcomm. > >> Generally, once something's upstreamed we expect it to remain supported. > > The V1 SOCs are technically pre-production, but still in wide use and > it will be a while before they are all replaced by V2 SOCs. It's only > because of the "ugliness" of the erratum and its work-around that we > want to git rid of it when we can. Interesting. How will you guarantee that nobody will ever want to run a mainline kernel on this box after a certain date? Self-destruct timer? ;-) As someone who runs mainline on HW that exceeded its "sell-by" date by a few decades, I'm genuinely interested. Thanks, M. -- Jazz is not dead, it just smell funny.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Christopher Covington <cov@codeaurora.org> - 2017-02-08 02:00 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi <timur@codeaurora.org> - 2017-02-08 05:10 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Christopher Covington <cov@codeaurora.org> - 2017-02-08 23:30 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi <timur@codeaurora.org> - 2017-02-09 00:10 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Robin Murphy <robin.murphy@arm.com> - 2017-02-08 13:30 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi <timur@codeaurora.org> - 2017-02-08 14:30 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Mark Rutland <mark.rutland@arm.com> - 2017-02-08 14:40 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi <timur@codeaurora.org> - 2017-02-08 16:30 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Marc Zyngier <marc.zyngier@arm.com> - 2017-02-08 17:00 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Timur Tabi <timur@codeaurora.org> - 2017-02-08 17:10 +0100
Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Christopher Covington <cov@codeaurora.org> - 2017-02-08 23:00 +0100
csiph-web