Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp5763525ybi; Sun, 21 Jul 2019 02:12:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqzv/Yr4E6t8zDF1KR7HAdfruifa7PgiQWLxI+e88N6EEn07cYq8NuDxLwyXA7fGzDh+tqd2 X-Received: by 2002:a17:902:be0a:: with SMTP id r10mr65044481pls.51.1563700328783; Sun, 21 Jul 2019 02:12:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563700328; cv=none; d=google.com; s=arc-20160816; b=nJt5On6YYL3KGw/Z3DtcAKgJYOQ+gZRrwm0C86oE43THJ7FhLls12jNJVWsxQydWlL QNhik0gHNgnVJnuw1rOObWJSZThXjPM3VQAquPDQETo4wzpJ2ujeJYYNJuFV1ykysQoG NwHXc9hGCW0qpiFdPhjgpeMjeYw+N5p5fho685b0zGaR65E8ccqrZzsLMk49e+GBgiNH DPVz3i4iVl0A4ulJU4H1FLAHHcDT8ljRFNyXl0EYTBFr4dsgxLM7J47ogdRTe0czRVth 0bGenp8V6lBGVpt645ckvB0//tYty8f8ysUi4F3iTcHsJ3mA3cvKLjG+7esGF/PwBh/d b8Vg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=PbP2X6NIQ0TsX6f4YAaWzUSD+G4Atkgs9bO3GMLpkFo=; b=iUUxj7gJebLkf2QUfnJtV9WYZ8uy2uiX4i7vslZDJtIyeynFE9YUZ7rPqUMYqsJwP3 nBHwVtEeO1NO2kTTHc+TZt2rMSqhvDjlDd1RGcc+RNoLhWSTX+7SRu/rxHYKZHbxgN1q QVnXQiG5Ag+9qDD029tboERelSDI9ULSH3hT9f+96yZLB2B8TQYHt1AL/BDbDvdfcbtj Lh3JjpxIzkFH68H2+eHVIXu6ubaEPAlALtC72fOePlVoowZ1LqoI+BqpdNxeGZbbzqqi GNpe5jHhQ7rCB38HwGTV53cN8SwtNXlBBpurUhQDKlzNZYRJ8QcyI33OT2SwX+wM2r77 YwKQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z7si7223917pfz.154.2019.07.21.02.11.50; Sun, 21 Jul 2019 02:12:08 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726074AbfGUJKN (ORCPT + 99 others); Sun, 21 Jul 2019 05:10:13 -0400 Received: from mail-qk1-f194.google.com ([209.85.222.194]:43380 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725851AbfGUJKN (ORCPT ); Sun, 21 Jul 2019 05:10:13 -0400 Received: by mail-qk1-f194.google.com with SMTP id m14so792775qka.10; Sun, 21 Jul 2019 02:10:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PbP2X6NIQ0TsX6f4YAaWzUSD+G4Atkgs9bO3GMLpkFo=; b=S8YBxnqkUM+kxxvnU5QZpqsAP8ZEEQVh2aL+5/6pYcwPD2TTOvWUQC2BUdbbTKWF2A aukBFJjR0yFqDX8C1Io5MA71icVNCoIb01RlJPM7eBasbNbJO7FfqLE4PJ1gr9vwAW0o FWlRTd1S9oaPJOQHPJZ1PuqNCJipWWRcXfsxAw8gY/WyCJN0AQ4b3lgAWJW5kjrKlaJn GD78X1JSiM+wimy0vEKBx4BxaiZpKtNxr4V/50ERWDwQ9GcmGPoFkWnfIOwpcz4ISwoe F4IsIVLOC6RdVbnHLrZO7u5epOIwE7EWOIOBaT089c6JQWlw2iiKpDWo3sRAqYE3gKvF 2SDw== X-Gm-Message-State: APjAAAWuJOyPUj0/iovPv3ZKtMH2Wf+DBQwaNai5kMT85g7NaJeIf1L/ kW2s6Xb2aMQ/6jEmV3yO74VRr+gJVMTz54UDJJ4= X-Received: by 2002:a37:4ac3:: with SMTP id x186mr40996804qka.138.1563700211845; Sun, 21 Jul 2019 02:10:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Arnd Bergmann Date: Sun, 21 Jul 2019 11:09:55 +0200 Message-ID: Subject: Re: [Question] orphan platform data header To: Masahiro Yamada , Ben Dooks Cc: Linux Kernel Mailing List , Linus Torvalds , Greg Kroah-Hartman , DTML , linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 21, 2019 at 5:45 AM Masahiro Yamada wrote: > On Sat, Jul 20, 2019 at 10:55 PM Arnd Bergmann wrote: > > On Sat, Jul 20, 2019 at 5:26 AM Masahiro Yamada wrote: > > > So, what shall we do? > > > > > > Drop the board-file support? Or, keep it > > > in case somebody is still using their board-files > > > in downstream? >> > > For this file, all boards got converted to DT, and the old setup > > code removed in commit ebc278f15759 ("ARM: mvebu: remove static > > LED setup for netxbig boards"), four years ago, so it's a fairly > > easy decision to make it DT only. > > I see another case, which is difficult > to make a decision. > > For example, drivers/spi/spi-tle62x0.c > > This driver supports only board-file, but the board-file > is not found in upstream. > > Unless I am terribly missing something, > there is no one who passes tle62x0_pdata > to this driver. > > $ git grep tle62x0_pdata > drivers/spi/spi-tle62x0.c: struct tle62x0_pdata *pdata; > include/linux/spi/tle62x0.h:struct tle62x0_pdata { > > But, removing board-file support > makes this driver completely useless... Adding Ben Dooks to Cc. I suspect this driver is completely obsolete and should be removed. For some reason, it's not an SPI controller driver like all the other files in that directory, but implements low-level access to the state of a particular SPI device. However, there should not really be a low-level driver for it that just exports the pins to user space. It should either be a gpiolib driver to let other drivers talk to the pins, or a high-level driver that exposes the intended functionality (watchdog, regulator, ...) to those respective subsystems. Arnd