From: Randy Dunlap <rdunlap@infradead.org>
To: "Hean-Loong, Ong" <hean.loong.ong@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, chin.liang.see@intel.com,
Ong@vger.kernel.org
Subject: Re: [PATCHv14 3/3] ARM:drm ivip Intel FPGA Video and Image Processing Suite
Date: Wed, 13 Mar 2019 13:35:53 -0700 [thread overview]
Message-ID: <fe101dca-2b39-fe0e-9bee-279abab9db8a@infradead.org> (raw)
In-Reply-To: <20190313202206.921-4-hean.loong.ong@intel.com>
On 3/13/19 1:22 PM, Hean-Loong, Ong wrote:
> diff --git a/drivers/gpu/drm/ivip/Kconfig b/drivers/gpu/drm/ivip/Kconfig
> new file mode 100644
> index 0000000..1d08b90
> --- /dev/null
> +++ b/drivers/gpu/drm/ivip/Kconfig
> @@ -0,0 +1,14 @@
> +config DRM_IVIP
> + tristate "Intel FGPA Video and Image Processing"
> + depends on DRM && OF
> + select DRM_GEM_CMA_HELPER
> + select DRM_KMS_HELPER
> + select DRM_KMS_FB_HELPER
> + select DRM_KMS_CMA_HELPER
> + help
> + Choose this option if you have an Intel FPGA Arria 10 system
> + and above with an Intel Display Port IP. This does not support
> + legacy Intel FPGA Cyclone V display port. Currently only single
> + frame buffer is supported. Note that ACPI and X_86 architecture
> + is not supported for Arria10. If M is selected the module will be
> + called ivip.
Hi,
If you make any changes to this series, the help text here is
indented too much. Just use one tab + 2 spaces, not 2 tabs + 2 spaces.
thanks.
--
~Randy
prev parent reply other threads:[~2019-03-13 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 20:22 [PATCHv14 0/3] Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
2019-03-13 20:22 ` [PATCHv14 1/3] ARM:dt-bindings:display " Hean-Loong, Ong
2019-03-13 20:22 ` [PATCHv14 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2019-03-13 20:22 ` [PATCHv14 3/3] ARM:drm ivip " Hean-Loong, Ong
2019-03-13 20:35 ` Randy Dunlap [this message]
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=fe101dca-2b39-fe0e-9bee-279abab9db8a@infradead.org \
--to=rdunlap@infradead.org \
--cc=Ong@vger.kernel.org \
--cc=chin.liang.see@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hean.loong.ong@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).