From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752098AbcFZR0U (ORCPT ); Sun, 26 Jun 2016 13:26:20 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:44222 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751687AbcFZR0S (ORCPT ); Sun, 26 Jun 2016 13:26:18 -0400 Date: Sun, 26 Jun 2016 18:25:40 +0100 From: Mark Brown To: Michal Suchanek Cc: Greg Kroah-Hartman , Ingo Molnar , Andrew Morton , Kees Cook , Thomas Gleixner , Dan Williams , Tejun Heo , "Paul E. McKenney" , Davidlohr Bueso , Andrey Ryabinin , Nikolay Aleksandrov , Dmitry Vyukov , Adrien Schildknecht , Linux Kernel Mailing List , linux-spi Message-ID: <20160626172540.GR28202@sirena.org.uk> References: <20160626011500.GF28202@sirena.org.uk> <20160626112133.GJ28202@sirena.org.uk> <20160626115815.GN28202@sirena.org.uk> <20160626124550.GO28202@sirena.org.uk> <20160626125717.GQ28202@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="opXR4bS/BgjGcxUR" Content-Disposition: inline In-Reply-To: X-Cookie: Beware of Bigfoot! 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 2/3] spi: of: allow instantiating slaves without a 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 --opXR4bS/BgjGcxUR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jun 26, 2016 at 05:19:54PM +0200, Michal Suchanek wrote: > On 26 June 2016 at 14:57, Mark Brown wrote: > > That would be a binding for the connector which is the big missing bit > > here - it's not clear that such a limited connector description would be > > a good idea. > It would work for a limited number of devices. Anyway, connectors are > supposed to be transparent so if binding devices has issues now it > will supposedly have same issues once connectors allow renaming > several devices at once from board-specific name to connector-specific > name rather than one at a time as this limited connector binding > allows. It's not entirely clear to me that connectors are going to end up transparent, at least to the host system - there's things like pinmuxing in there. They're a definite thing and some work needs to go into hiding them from the plugin modules, work which might mean that these dummy nodes don't need to be created. In any case this series needs a bunch of restructuring, some of it needs replacing and the whole thing needs to be presented a lot more clearly. --opXR4bS/BgjGcxUR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXcBATAAoJECTWi3JdVIfQWbMIAIJ8cqANcG6kgOaJOoEYEDRQ g2++NfXziNH9ChKJCoNb6MuO5CAYywW3cRDSa3D7DSC/Fm55kCK+kqpcUAcKQluo nqS62i5E99PGqwXivIvht1jZDo6NSyyLONhCF7bfvoIJe308d2JE1bs32RAxknKO NyxN/C6j/PaVPJVFxYjYgRypXyOXQObTK/9WVvLyfJ1Bwi/ws0khWfHvIdBy7Yca gvtIWZYX4ab9KBhmLvAYWEgKsGYqkmGNQvcLk8qaqIM8fnzpx9HVcMSf4YFENxBR Nhj/JxS+42G+f+Mg1cvD8O+iFOLY7yfyt2PmdPhLCjHZ5bxDWQKdz616ikPl3GU= =0yqN -----END PGP SIGNATURE----- --opXR4bS/BgjGcxUR--