From: Christoph Hellwig <hch@infradead.org>
To: Christian K??nig <christian.koenig@amd.com>
Cc: Bhawanpreet.Lakha@amd.com, Harry.Wentland@amd.com,
Anson Jacob <Anson.Jacob@amd.com>,
qingqing.zhuo@amd.com, Rodrigo.Siqueira@amd.com,
linux-kernel@vger.kernel.org, roman.li@amd.com,
Christoph Hellwig <hch@infradead.org>,
Sunpeng.Li@amd.com, Aurabindo.Pillai@amd.com, paulus@samba.org,
amd-gfx@lists.freedesktop.org, linuxppc-dev@lists.ozlabs.org,
bindu.r@amd.com
Subject: Re: [RFC v2 2/2] drm/amd/display: Use PPC FPU functions
Date: Wed, 21 Jul 2021 07:51:53 +0100 [thread overview]
Message-ID: <YPfECUtD0SRCjrSm@infradead.org> (raw)
In-Reply-To: <9094cea1-602e-6e71-4ff7-c06fd04af6c5@amd.com>
On Wed, Jul 21, 2021 at 08:29:43AM +0200, Christian K??nig wrote:
> Looks good in general, but question is what about other architectures like
> ARM?
DRM_AMD_DC_DCN currently requires X86 || PPC64.
Maybe a good think would be to add a new KERNEL_FPU_API Kconfig symbol,
selected by x86 and powerpc (I think ppc32 should be fine too now) so
that we get these arch dependencies out of the driver.
next prev parent reply other threads:[~2021-07-21 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 4:47 [RFC v2 0/2] PPC: Add generic FPU api similar to x86 Anson Jacob
2021-07-21 4:48 ` [RFC v2 1/2] ppc/fpu: " Anson Jacob
2021-07-21 6:58 ` Christoph Hellwig
2021-07-21 4:48 ` [RFC v2 2/2] drm/amd/display: Use PPC FPU functions Anson Jacob
2021-07-21 6:29 ` Christian König
2021-07-21 6:51 ` Christoph Hellwig [this message]
2021-07-21 9:24 ` Christian König
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=YPfECUtD0SRCjrSm@infradead.org \
--to=hch@infradead.org \
--cc=Anson.Jacob@amd.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bindu.r@amd.com \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=qingqing.zhuo@amd.com \
--cc=roman.li@amd.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;
as well as URLs for NNTP newsgroup(s).