From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1677C4338F for ; Fri, 23 Jul 2021 19:20:58 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2171660BD3 for ; Fri, 23 Jul 2021 19:20:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 2171660BD3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4GWfLH0rzQz3cjw for ; Sat, 24 Jul 2021 05:20:55 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=intel.com (client-ip=134.134.136.65; helo=mga03.intel.com; envelope-from=andriy.shevchenko@intel.com; receiver=) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4GWfKr3QjFz2xtr for ; Sat, 24 Jul 2021 05:20:26 +1000 (AEST) X-IronPort-AV: E=McAfee;i="6200,9189,10054"; a="211998071" X-IronPort-AV: E=Sophos;i="5.84,264,1620716400"; d="scan'208";a="211998071" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jul 2021 12:19:22 -0700 X-IronPort-AV: E=Sophos;i="5.84,264,1620716400"; d="scan'208";a="471629902" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jul 2021 12:19:20 -0700 Received: from andy by smile with local (Exim 4.94.2) (envelope-from ) id 1m70hV-00HTx9-M4; Fri, 23 Jul 2021 22:19:13 +0300 Date: Fri, 23 Jul 2021 22:19:13 +0300 From: Andy Shevchenko To: Christian Lamparter Subject: Re: [PATCH v3 0/5] powerpc: apm82181: adding customer devices Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, Chris Blake , Rob Herring , Paul Mackerras , linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Sun, Sep 06, 2020 at 12:06:10AM +0200, Christian Lamparter wrote: > Hello, > > I've been holding on to these devices dts' for a while now. > But ever since the recent purge of the PPC405, I'm feeling > the urge to move forward. > > The devices in question have been running with OpenWrt since > around 2016/2017. Back then it was linux v4.4 and required > many out-of-tree patches (for WIFI, SATA, CRYPTO...), that > since have been integrated. So, there's nothing else in the > way I think. > > A patch that adds the Meraki vendor-prefix has been sent > separately, as there's also the Meraki MR32 that I'm working > on as well. Here's the link to the patch: > > > Now, I've looked around in the arch/powerpc for recent .dts > and device submissions to get an understanding of what is > required. > >From the looks of it, it seems like every device gets a > skeleton defconfig and a CONFIG_$DEVICE symbol (Like: > CONFIG_MERAKI_MR24, CONFIG_WD_MYBOOKLIVE). > > Will this be the case? Or would it make sense to further > unite the Bluestone, MR24 and MBL under a common CONFIG_APM82181 > and integrate the BLUESTONE device's defconfig into it as well? > (I've stumbled across the special machine compatible > handling of ppc in the Documentation/devicetree/usage-model.rst > already.) I haven't found any traces of this to be applied. What is the status of this patch series? And what is the general state of affairs for the PPC44x? -- With Best Regards, Andy Shevchenko From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C7F5BC4338F for ; Fri, 23 Jul 2021 19:19:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A926460EB2 for ; Fri, 23 Jul 2021 19:19:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229528AbhGWSiu (ORCPT ); Fri, 23 Jul 2021 14:38:50 -0400 Received: from mga18.intel.com ([134.134.136.126]:12357 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229461AbhGWSiu (ORCPT ); Fri, 23 Jul 2021 14:38:50 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10054"; a="199199000" X-IronPort-AV: E=Sophos;i="5.84,264,1620716400"; d="scan'208";a="199199000" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jul 2021 12:19:22 -0700 X-IronPort-AV: E=Sophos;i="5.84,264,1620716400"; d="scan'208";a="471629902" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jul 2021 12:19:20 -0700 Received: from andy by smile with local (Exim 4.94.2) (envelope-from ) id 1m70hV-00HTx9-M4; Fri, 23 Jul 2021 22:19:13 +0300 Date: Fri, 23 Jul 2021 22:19:13 +0300 From: Andy Shevchenko To: Christian Lamparter Cc: linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org, Chris Blake , Paul Mackerras , Benjamin Herrenschmidt , Michael Ellerman , Rob Herring Subject: Re: [PATCH v3 0/5] powerpc: apm82181: adding customer devices Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Sun, Sep 06, 2020 at 12:06:10AM +0200, Christian Lamparter wrote: > Hello, > > I've been holding on to these devices dts' for a while now. > But ever since the recent purge of the PPC405, I'm feeling > the urge to move forward. > > The devices in question have been running with OpenWrt since > around 2016/2017. Back then it was linux v4.4 and required > many out-of-tree patches (for WIFI, SATA, CRYPTO...), that > since have been integrated. So, there's nothing else in the > way I think. > > A patch that adds the Meraki vendor-prefix has been sent > separately, as there's also the Meraki MR32 that I'm working > on as well. Here's the link to the patch: > > > Now, I've looked around in the arch/powerpc for recent .dts > and device submissions to get an understanding of what is > required. > >From the looks of it, it seems like every device gets a > skeleton defconfig and a CONFIG_$DEVICE symbol (Like: > CONFIG_MERAKI_MR24, CONFIG_WD_MYBOOKLIVE). > > Will this be the case? Or would it make sense to further > unite the Bluestone, MR24 and MBL under a common CONFIG_APM82181 > and integrate the BLUESTONE device's defconfig into it as well? > (I've stumbled across the special machine compatible > handling of ppc in the Documentation/devicetree/usage-model.rst > already.) I haven't found any traces of this to be applied. What is the status of this patch series? And what is the general state of affairs for the PPC44x? -- With Best Regards, Andy Shevchenko