From: Randy Dunlap <rdunlap@infradead.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
LKML <linux-kernel@vger.kernel.org>
Cc: linux-ide@vger.kernel.org, linux-fbdev@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
linux-nvme@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Initialize ATA before graphics
Date: Tue, 25 Feb 2020 08:33:29 -0800 [thread overview]
Message-ID: <0da5bb70-2e55-0fa2-d950-3832f9ff7bcd@infradead.org> (raw)
In-Reply-To: <041f4abd-f894-b990-b320-bf0aab4242f2@molgen.mpg.de>
Hi Paul,
You should have also Cc-ed Arjan on this email. [done]
On 2/24/20 6:09 AM, Paul Menzel wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Thu, 2 Jun 2016 23:36:32 -0500
>
> ATA init is the long pole in the boot process, and its asynchronous.
> Move the graphics init after it, so that ATA and graphics initialize
> in parallel.
>
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
> ---
>
> 1. Taken from Clear Linux: https://github.com/clearlinux-pkgs/linux/commits/master/0110-Initialize-ata-before-graphics.patch
> 2. Arjan, can you please add your Signed-off-by line?
>
> drivers/Makefile | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/Makefile b/drivers/Makefile
> index aaef17c..d08f3a3 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -58,15 +58,8 @@ obj-y += char/
> # iommu/ comes before gpu as gpu are using iommu controllers
> obj-y += iommu/
>
> -# gpu/ comes after char for AGP vs DRM startup and after iommu
> -obj-y += gpu/
> -
> obj-$(CONFIG_CONNECTOR) += connector/
>
> -# i810fb and intelfb depend on char/agp/
> -obj-$(CONFIG_FB_I810) += video/fbdev/i810/
> -obj-$(CONFIG_FB_INTEL) += video/fbdev/intelfb/
> -
> obj-$(CONFIG_PARPORT) += parport/
> obj-$(CONFIG_NVM) += lightnvm/
> obj-y += base/ block/ misc/ mfd/ nfc/
> @@ -79,6 +72,14 @@ obj-$(CONFIG_IDE) += ide/
> obj-y += scsi/
> obj-y += nvme/
> obj-$(CONFIG_ATA) += ata/
> +
> +# gpu/ comes after char for AGP vs DRM startup and after iommu
> +obj-y += gpu/
> +
> +# i810fb and intelfb depend on char/agp/
> +obj-$(CONFIG_FB_I810) += video/fbdev/i810/
> +obj-$(CONFIG_FB_INTEL) += video/fbdev/intelfb/
> +
> obj-$(CONFIG_TARGET_CORE) += target/
> obj-$(CONFIG_MTD) += mtd/
> obj-$(CONFIG_SPI) += spi/
>
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-02-25 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 14:09 [PATCH] Initialize ATA before graphics Paul Menzel
2020-02-25 16:33 ` 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=0da5bb70-2e55-0fa2-d950-3832f9ff7bcd@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@linux.ie \
--cc=arjan@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=hdegoede@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pmenzel@molgen.mpg.de \
--cc=sagi@grimberg.me \
/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).