Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Ben Whitten <Ben.Whitten@lairdtech.com>
To:     Mark Brown <broonie@kernel.org>,
        =?iso-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
CC:     "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Jian-Hong Pan <starnight@g.ncu.edu.tw>,
        Jiri Pirko <jiri@resnulli.us>,
        Marcel Holtmann <marcel@holtmann.org>,
        "David S . Miller" <davem@davemloft.net>,
        Matthias Brugger <mbrugger@suse.com>,
        Janus Piwek <jpiwek@arroweurope.com>,
        =?iso-8859-1?Q?Michael_R=F6der?= <michael.roeder@avnet.eu>,
        Dollar Chen <dollar.chen@wtmec.com>,
        Ken Yu <ken.yu@rakwireless.com>,
        Steve deRosier <derosier@gmail.com>,
        "linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
        "LoRa_Community_Support@semtech.com" 
        <LoRa_Community_Support@semtech.com>,
        Hasnain Virk <Hasnain.Virk@arm.com>
Subject: RE: [RFC net-next 15/15] net: lora: Add Semtech SX1301
Thread-Topic: [RFC net-next 15/15] net: lora: Add Semtech SX1301
Thread-Index: AQHUESvvwSr5pLbXbkmh3lgaa2XdVqR8HL0AgAAWvYCAAWSEAIAABWIAgAAGJICAABNMgIABP2uAgAAdtsA=
Date:   Wed, 4 Jul 2018 13:41:42 +0000
Message-ID: <BY1PR02MB1114BC0F12654B1E7C614108E7410@BY1PR02MB1114.namprd02.prod.outlook.com>
References: <20180701110804.32415-1-afaerber@suse.de>
 <20180701110804.32415-16-afaerber@suse.de>
 <20180702161258.GA18744@sirena.org.uk>
 <4e06cc72-2092-70f3-c801-bf6e4c3cbec2@suse.de>
 <20180703145022.GA13744@sirena.org.uk>
 <809fc546-6012-37f3-9485-cfd8eaf99488@suse.de>
 <20180703153137.GB13744@sirena.org.uk>
 <3f6289f9-d345-39a7-f0dd-9d5fa7c86e82@suse.de>
 <20180704114355.GB11693@sirena.org.uk>
In-Reply-To: <20180704114355.GB11693@sirena.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: lairdtech.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a351dc9-1897-4f34-5e53-08d5e1b3e101
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jul 2018 13:41:43.0819
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c4d27a54-2db1-4088-a044-1a83c778ad1b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR02MB1259
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> Subject: Re: [RFC net-next 15/15] net: lora: Add Semtech SX1301
>=20
> On Tue, Jul 03, 2018 at 06:40:41PM +0200, Andreas F=E4rber wrote:
>=20
> > Do you have an alternative solution for abstraction? A regmap would see=
m
> > to require putting everything into a monolithic SX1301 driver despite
> > those connected chipsets actually being regular, external SPI chips tha=
t
> > could also be attached to non-SX1301 SPI masters.
>=20
> I'm suggesting a regmap for those external SPI chips.  It doesn't matter
> what the host uses.

Currently in my testing drivers I have used regmap for both the SX1301 and =
the downstream SX1257.
In my SX1257 driver currently the regmap is backed via SPI with devm_regmap=
_init_spi, please correct me if I am wrong but if I understand correctly th=
is could be split out to regmap backed by SPI in the case of a direct host =
connection, and a regmap backed by the SX1301's regmapped strobing register=
 interface, regmap_bus?
Is there a precedent to this I can examine?