From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752369AbcF1Sih (ORCPT ); Tue, 28 Jun 2016 14:38:37 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:52518 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751977AbcF1Sif (ORCPT ); Tue, 28 Jun 2016 14:38:35 -0400 Date: Tue, 28 Jun 2016 19:38:25 +0100 From: Mark Brown To: Michal Suchanek Cc: Greg Kroah-Hartman , Linux Kernel Mailing List , linux-spi Message-ID: <20160628183825.GS17217@sirena.org.uk> References: <15ff382f699387e2d8f23779db851d0de7e9291e.1467053363.git.hramrach@gmail.com> <20160627190949.GB5111@kroah.com> <20160627221259.GA10054@kroah.com> <20160628155107.GP17217@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tgGnixv3tJWXBxdL" Content-Disposition: inline In-Reply-To: X-Cookie: Last week's pet, this week's special. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --tgGnixv3tJWXBxdL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --tgGnixv3tJWXBxdL Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXcsQgAAoJECTWi3JdVIfQPeMIAIWEIixwqwnZDZqPdpm70CFF ZfnTH4ZR4SU3iXqYe8dkW69Eu0pGSLH7P9uCmZlBJwkC0UO4OZhgzBIDCPfuC7Gh KuK4iUuD/ijPvmL7RUKpsc9S+W64foERuIKWW0Kb/IvcNC3AjPmBtC/7jhTeYYug mfoSJTA6CTJ/dzKG3SgCkTEqn457s7BsUw/+OeNIvos3k8QpqtIe2rpX0jaB2Sx+ gXqkocT8CjB7qiEaBoF1Zj6yAGhiC83om/4a8CPv9GrLAy2GkU6VUFb9yOtu4r0n MVuZ3QTZ/A6W0M6eyJYwclW1BPxB7Ndnut+9ibEMI8s+4s7Zjb9Hg7Il+UDejx8= =8k+Y -----END PGP SIGNATURE----- --tgGnixv3tJWXBxdL--