From: Mark Brown <broonie@kernel.org> To: Michal Suchanek <hramrach@gmail.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-spi <linux-spi@vger.kernel.org> Subject: Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver Date: Tue, 28 Jun 2016 19:38:25 +0100 [thread overview] Message-ID: <20160628183825.GS17217@sirena.org.uk> (raw) In-Reply-To: <CAOMqctQbFmWv04idz7G+dPOCg7n-E0AQdhGAyohUDBniKvrP_g@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1600 bytes --] On Tue, Jun 28, 2016 at 06:24:58PM +0200, Michal Suchanek wrote: > No, no, no! > This is NOT about loading an overlay. This is about talking on the bus > without loading an overlay. This is the solution you want to adopt because you've decided that it's what you want. You've said this quite a number of times now. > > Repeating yourself over and over again is not going to help here, it's > > just going to make people more annoyed. Please stop this. > Then please add something constructive to the debate rather than > repeating that users have to add compatible for devices used with > userspace driver. That's ridiculous from usability point of view and > so will never happen. At best workarounds for kernel obtuseness will > be used. It would take a lot less effort for you to just describe your hardware in DT than it would for you to continue repeating yourself, this is a trivial task. If the tooling around this is too hard to use then that seems like a useful thing to work on, having simple ways for people to describe modules they build for maker type systems (ideally integrated with schematic capture software) would be great for example. Both Greg and myself have provided you with feedback which you appear to be ignoring entirely. What you are demanding is not idiomatic for DT or for the device model, this needs to be taken on board rather than just shouting at us. Putting a quick hack in that happens to work for your very specific use case isn't going to give us a consistent, maintainable and well designed system if it doesn't fit with anything else we're doing. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Michal Suchanek <hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>, Linux Kernel Mailing List <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver Date: Tue, 28 Jun 2016 19:38:25 +0100 [thread overview] Message-ID: <20160628183825.GS17217@sirena.org.uk> (raw) In-Reply-To: <CAOMqctQbFmWv04idz7G+dPOCg7n-E0AQdhGAyohUDBniKvrP_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> [-- Attachment #1: Type: text/plain, Size: 1600 bytes --] On Tue, Jun 28, 2016 at 06:24:58PM +0200, Michal Suchanek wrote: > No, no, no! > This is NOT about loading an overlay. This is about talking on the bus > without loading an overlay. This is the solution you want to adopt because you've decided that it's what you want. You've said this quite a number of times now. > > Repeating yourself over and over again is not going to help here, it's > > just going to make people more annoyed. Please stop this. > Then please add something constructive to the debate rather than > repeating that users have to add compatible for devices used with > userspace driver. That's ridiculous from usability point of view and > so will never happen. At best workarounds for kernel obtuseness will > be used. It would take a lot less effort for you to just describe your hardware in DT than it would for you to continue repeating yourself, this is a trivial task. If the tooling around this is too hard to use then that seems like a useful thing to work on, having simple ways for people to describe modules they build for maker type systems (ideally integrated with schematic capture software) would be great for example. Both Greg and myself have provided you with feedback which you appear to be ignoring entirely. What you are demanding is not idiomatic for DT or for the device model, this needs to be taken on board rather than just shouting at us. Putting a quick hack in that happens to work for your very specific use case isn't going to give us a consistent, maintainable and well designed system if it doesn't fit with anything else we're doing. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-28 18:38 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-27 19:02 [PATCH v2 0/3] Updated spidev usability patchset Michal Suchanek 2016-06-27 19:02 ` Michal Suchanek 2016-06-27 19:02 ` [PATCH v2 1/3] spi: spidev: fix the check for spidev in dt Michal Suchanek 2016-06-27 20:36 ` Mark Brown 2016-06-27 20:36 ` Mark Brown 2016-06-27 19:02 ` [PATCH v2 2/3] spi: of: allow instantiating slaves without a driver Michal Suchanek 2016-06-27 21:14 ` Mark Brown 2016-06-27 21:14 ` Mark Brown 2016-06-27 19:02 ` [PATCH v2 3/3] drivers core: allow id match override when manually binding driver Michal Suchanek 2016-06-27 19:02 ` Michal Suchanek 2016-06-27 19:09 ` Greg Kroah-Hartman 2016-06-27 19:09 ` Greg Kroah-Hartman 2016-06-27 19:40 ` Michal Suchanek 2016-06-27 19:40 ` Michal Suchanek 2016-06-27 20:32 ` Mark Brown 2016-06-27 20:32 ` Mark Brown 2016-06-27 22:12 ` Greg Kroah-Hartman 2016-06-27 22:12 ` Greg Kroah-Hartman 2016-06-28 12:40 ` Michal Suchanek 2016-06-28 12:40 ` Michal Suchanek 2016-06-28 15:51 ` Mark Brown 2016-06-28 15:51 ` Mark Brown 2016-06-28 16:24 ` Michal Suchanek 2016-06-28 16:24 ` Michal Suchanek 2016-06-28 18:38 ` Mark Brown [this message] 2016-06-28 18:38 ` Mark Brown 2016-06-28 20:02 ` Michal Suchanek 2016-06-28 20:57 ` Mark Brown 2016-06-28 20:57 ` Mark Brown 2016-06-29 3:32 ` Michal Suchanek 2016-06-29 3:32 ` Michal Suchanek 2016-06-29 18:02 ` Mark Brown 2016-06-29 18:02 ` Mark Brown 2016-06-30 7:47 ` Michal Suchanek 2016-06-30 7:47 ` Michal Suchanek 2016-06-30 9:03 ` Dan O'Donovan 2016-06-30 9:03 ` Dan O'Donovan 2016-07-01 9:36 ` Mark Brown 2016-07-01 10:11 ` Michal Suchanek 2016-07-01 10:11 ` Michal Suchanek 2016-07-01 8:25 ` Mark Brown 2016-07-01 8:58 ` Michal Suchanek 2016-07-01 8:58 ` Michal Suchanek 2016-07-01 15:00 ` Mark Brown 2016-07-01 15:37 ` Michal Suchanek 2016-07-01 16:22 ` Mark Brown 2016-07-01 18:56 ` Michal Suchanek 2016-07-01 18:56 ` Michal Suchanek 2016-07-01 19:36 ` Michal Suchanek 2016-07-01 19:36 ` Michal Suchanek
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=20160628183825.GS17217@sirena.org.uk \ --to=broonie@kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=hramrach@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.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: 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.