From: Mark Brown <broonie@kernel.org> To: "Rafael J. Wysocki" <rafael@kernel.org> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, ACPI Devel Maling List <linux-acpi@vger.kernel.org>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-gpio@vger.kernel.org, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, linux-pwm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>, alsa-devel@alsa-project.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org> Subject: Re: [PATCH v2 01/12] device: property: delay device-driver matches Date: Fri, 17 Jul 2015 01:06:22 +0100 [thread overview] Message-ID: <20150717000622.GH1602@sirena.org.uk> (raw) In-Reply-To: <CAJZ5v0gMx=DA0f8i9wdMvkYTyOhr0WKh-T6L7rjcxeaAjNMW3g@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1448 bytes --] On Fri, Jul 17, 2015 at 01:41:16AM +0200, Rafael J. Wysocki wrote: > On Thu, Jul 16, 2015 at 10:23 PM, Mark Brown <broonie@kernel.org> wrote: > > On Wed, Jul 01, 2015 at 11:40:56AM +0200, Tomeu Vizoso wrote: > > I have to say I'm still not 100% clear that special casing platform > > devices makes sense here - I can see that platform devices are usually > > the first devices to instantiate but there are other kinds of devices > > and it's not obvious what the benefit of specifically picking out > > platform devices as opposed to just deferring all devices is. > Some existing devices cannot be deferred without redesigning things quite a bit. OK, that should go in the changelog then - right now it's just a bit obtuse why we're doing this (and as you say it's a bit awkward). Now you mention this I'm thinking that some of the affected devices might be platform devices on some systems, IOMMUs spring to mind for example... they're one of the main bits of the system I'm aware of that still rely on probe ordering and they do tend to be platform devices. > What I was talking about, though, was to use an opt-in mechanism for > that which could be set for all platform devices, for example, by > default, but it might be set for other bus types too if that's useful. Sure, I got that and do agree with you that a mechanism like you suggest would be good. I just wasn't clear why we were targetting platform devices in the first place. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: "Rafael J. Wysocki" <rafael@kernel.org> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, ACPI Devel Maling List <linux-acpi@vger.kernel.org>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-gpio@vger.kernel.org, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, linux-pwm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>, alsa-devel@alsa-project.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org> Subject: Re: [PATCH v2 01/12] device: property: delay device-driver matches Date: Fri, 17 Jul 2015 00:06:22 +0000 [thread overview] Message-ID: <20150717000622.GH1602@sirena.org.uk> (raw) In-Reply-To: <CAJZ5v0gMx=DA0f8i9wdMvkYTyOhr0WKh-T6L7rjcxeaAjNMW3g@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1448 bytes --] On Fri, Jul 17, 2015 at 01:41:16AM +0200, Rafael J. Wysocki wrote: > On Thu, Jul 16, 2015 at 10:23 PM, Mark Brown <broonie@kernel.org> wrote: > > On Wed, Jul 01, 2015 at 11:40:56AM +0200, Tomeu Vizoso wrote: > > I have to say I'm still not 100% clear that special casing platform > > devices makes sense here - I can see that platform devices are usually > > the first devices to instantiate but there are other kinds of devices > > and it's not obvious what the benefit of specifically picking out > > platform devices as opposed to just deferring all devices is. > Some existing devices cannot be deferred without redesigning things quite a bit. OK, that should go in the changelog then - right now it's just a bit obtuse why we're doing this (and as you say it's a bit awkward). Now you mention this I'm thinking that some of the affected devices might be platform devices on some systems, IOMMUs spring to mind for example... they're one of the main bits of the system I'm aware of that still rely on probe ordering and they do tend to be platform devices. > What I was talking about, though, was to use an opt-in mechanism for > that which could be set for all platform devices, for example, by > default, but it might be set for other bus types too if that's useful. Sure, I got that and do agree with you that a mechanism like you suggest would be good. I just wasn't clear why we were targetting platform devices in the first place. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-17 0:06 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-01 9:40 [PATCH v2 0/12] Discover and probe dependencies Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` [PATCH v2 01/12] device: property: delay device-driver matches Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 23:29 ` Rafael J. Wysocki 2015-07-01 23:29 ` Rafael J. Wysocki 2015-07-10 11:39 ` Tomeu Vizoso 2015-07-10 11:39 ` Tomeu Vizoso 2015-07-10 11:39 ` Tomeu Vizoso 2015-07-16 20:23 ` Mark Brown 2015-07-16 20:23 ` Mark Brown [not found] ` <20150716202312.GD11162-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2015-07-16 23:41 ` Rafael J. Wysocki 2015-07-16 23:41 ` Rafael J. Wysocki 2015-07-16 23:41 ` Rafael J. Wysocki 2015-07-17 0:06 ` Mark Brown [this message] 2015-07-17 0:06 ` Mark Brown 2015-07-01 9:40 ` [PATCH v2 02/12] device: property: find dependencies of a firmware node Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 23:36 ` Rafael J. Wysocki 2015-07-02 0:02 ` Rafael J. Wysocki 2015-07-10 13:14 ` [alsa-devel] " Tomeu Vizoso 2015-07-10 13:14 ` Tomeu Vizoso 2015-07-10 13:14 ` Tomeu Vizoso 2015-07-11 2:52 ` Rafael J. Wysocki 2015-07-11 2:52 ` [alsa-devel] " Rafael J. Wysocki 2015-07-11 2:52 ` Rafael J. Wysocki 2015-07-01 9:40 ` [PATCH v2 03/12] string: Introduce strends() Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` [PATCH v2 04/12] gpio: register dependency parser for firmware nodes Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:40 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 05/12] gpu: host1x: " Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 06/12] backlight: Document consumers of backlight nodes Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 07/12] backlight: register dependency parser for firmware nodes Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 08/12] USB: EHCI: " Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 09/12] regulator: " Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-16 21:38 ` Mark Brown 2015-07-16 21:38 ` Mark Brown 2015-07-01 9:41 ` [PATCH v2 10/12] pwm: " Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` [PATCH v2 11/12] ASoC: tegra: " Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 17:38 ` Mark Brown 2015-07-01 17:38 ` Mark Brown 2015-07-13 12:10 ` [alsa-devel] " Tomeu Vizoso 2015-07-13 12:10 ` Tomeu Vizoso 2015-07-13 12:10 ` Tomeu Vizoso [not found] ` <CAAObsKDsEuDS46rW9CMuviDEDV-OVXe5q-kiWmw0D_n2D3Tf5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2015-07-13 15:42 ` Mark Brown 2015-07-13 15:42 ` Mark Brown 2015-07-13 15:42 ` Mark Brown 2015-07-14 7:34 ` Tomeu Vizoso 2015-07-14 7:34 ` Tomeu Vizoso 2015-07-14 7:34 ` Tomeu Vizoso [not found] ` <CAAObsKAVY7-QpcRyT4juc2RyB+vqibvzKO7wFCT2VsL9R8bzPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2015-07-14 11:07 ` Mark Brown 2015-07-14 11:07 ` Mark Brown 2015-07-14 11:07 ` Mark Brown 2015-07-14 12:47 ` Tomeu Vizoso 2015-07-14 12:47 ` Tomeu Vizoso 2015-07-14 12:47 ` Tomeu Vizoso 2015-07-16 23:04 ` Mark Brown 2015-07-16 23:04 ` Mark Brown 2015-07-01 9:41 ` [PATCH v2 12/12] driver-core: probe dependencies before probing Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso 2015-07-01 9:41 ` Tomeu Vizoso
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=20150717000622.GH1602@sirena.org.uk \ --to=broonie@kernel.org \ --cc=alsa-devel@alsa-project.org \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=gregkh@linuxfoundation.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pwm@vger.kernel.org \ --cc=rafael@kernel.org \ --cc=rjw@rjwysocki.net \ --cc=tomeu.vizoso@collabora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.