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=-1.0 required=3.0 tests=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 175C2C4740C for ; Mon, 9 Sep 2019 15:09:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E6ED720863 for ; Mon, 9 Sep 2019 15:09:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732994AbfIIPJI (ORCPT ); Mon, 9 Sep 2019 11:09:08 -0400 Received: from mail-qk1-f196.google.com ([209.85.222.196]:39789 "EHLO mail-qk1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727772AbfIIPJH (ORCPT ); Mon, 9 Sep 2019 11:09:07 -0400 Received: by mail-qk1-f196.google.com with SMTP id 4so13380260qki.6; Mon, 09 Sep 2019 08:09:07 -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=BRd75HfAMA/RM+2IUVcveN8rNVBoGEbq4cpvizDx7NM=; b=b43IxwCOSugVQGiMNJ1lDuBpsyM6wNPt+oC0fXNLqhUzBc3syZRR2dy47FKLc6uzTG 2jKst0dekoCrDj4nYjYrMoR+GjImMPjNgUQv7uaT7optxKeGs3SK4BekV65Il44d+V+V niTPDMFIgtX+QEq4B7NVW6zhQbQrpTFaEwHaq35ATmsAcXAaPe7BlXdEvhR2jda+4xiM dbnG6e7ts8awB9VCFR67PG4id+QZIvm/WqZPivGpB5lT0apXGBjMtYAS9gOc1alwXxKX DjLsDH5uH5xGNxBt41fFhF/VT1EQKidpajFdZ2ADnaZEth4K5zHhrUrVa28nsJwZizP0 16mQ== X-Gm-Message-State: APjAAAV9N2qg+HITI1b9x0FI/rZeIj0tmMZiX8A0sxAXReVNkUpMD5si fR0CZ+U/VFCfcvei/N1G+HhFUgCQUjPKhK8erVM= X-Google-Smtp-Source: APXvYqyixTPG+CFUK1hDkQTl3ReqfwNBD/A6zafQDgbntwdHXHwkh+RNO8Na4ISyGRsSqSCfU/vXAgp7FItNdTdN170= X-Received: by 2002:ae9:ee06:: with SMTP id i6mr3208112qkg.3.1568041746371; Mon, 09 Sep 2019 08:09:06 -0700 (PDT) MIME-Version: 1.0 References: <1568020220-7758-1-git-send-email-talel@amazon.com> <1568020220-7758-4-git-send-email-talel@amazon.com> <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> In-Reply-To: <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> From: Arnd Bergmann Date: Mon, 9 Sep 2019 17:08:50 +0200 Message-ID: Subject: Re: [PATCH 3/3] arm64: alpine: select AL_POS To: "Shenhar, Talel" Cc: Rob Herring , Mark Rutland , Mauro Carvalho Chehab , David Miller , gregkh , Nicolas Ferre , Thomas Gleixner , Patrick Venture , Linus Walleij , Olof Johansson , Maxime Ripard , Santosh Shilimkar , paul.kocialkowski@bootlin.com, mjourdan@baylibre.com, Catalin Marinas , Will Deacon , DTML , "linux-kernel@vger.kernel.org" , Linux ARM , David Woodhouse , Benjamin Herrenschmidt , hhhawa@amazon.com, ronenk@amazon.com, jonnyc@amazon.com, hanochu@amazon.com, barakw@amazon.com 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 Mon, Sep 9, 2019 at 3:59 PM Shenhar, Talel wrote: > On 9/9/2019 4:45 PM, Arnd Bergmann wrote: > > Its not that something will get broken. its error event detector for POS > events which allows seeing bad accesses to registers. > > What is the general rule of which configs to put under select and which > under defconfig? > > I was thinking that "general" SoC support is good under select - those > things that we always want. I generally want as little as possible to be selected, basically only things that are required for linking the kernel and booting it without potentially destroying the hardware. In particular, I want most drivers to be enabled as loadable modules if possible. When you have general-purpose distributions support your platform, there is no need to have this module built-in while running on a different chip, even if you always want to load the module when it's running on yours. > And specific features, e.g. RAID support or features that supported only > on specific HW shall go under defconfig. > > Similar, I see ARCH_LAYERSCAPE selecting EDAC_SUPPORT. I think this was done to avoid a link failure. It's also possible that this is a mistake and just did not get caught in review. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 3/3] arm64: alpine: select AL_POS Date: Mon, 9 Sep 2019 17:08:50 +0200 Message-ID: References: <1568020220-7758-1-git-send-email-talel@amazon.com> <1568020220-7758-4-git-send-email-talel@amazon.com> <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> Sender: linux-kernel-owner@vger.kernel.org To: "Shenhar, Talel" Cc: Rob Herring , Mark Rutland , Mauro Carvalho Chehab , David Miller , gregkh , Nicolas Ferre , Thomas Gleixner , Patrick Venture , Linus Walleij , Olof Johansson , Maxime Ripard , Santosh Shilimkar , paul.kocialkowski@bootlin.com, mjourdan@baylibre.com, Catalin Marinas , Will Deacon , DTML , "linux-kernel@vger.kernel.org" , Linux ARM David List-Id: devicetree@vger.kernel.org On Mon, Sep 9, 2019 at 3:59 PM Shenhar, Talel wrote: > On 9/9/2019 4:45 PM, Arnd Bergmann wrote: > > Its not that something will get broken. its error event detector for POS > events which allows seeing bad accesses to registers. > > What is the general rule of which configs to put under select and which > under defconfig? > > I was thinking that "general" SoC support is good under select - those > things that we always want. I generally want as little as possible to be selected, basically only things that are required for linking the kernel and booting it without potentially destroying the hardware. In particular, I want most drivers to be enabled as loadable modules if possible. When you have general-purpose distributions support your platform, there is no need to have this module built-in while running on a different chip, even if you always want to load the module when it's running on yours. > And specific features, e.g. RAID support or features that supported only > on specific HW shall go under defconfig. > > Similar, I see ARCH_LAYERSCAPE selecting EDAC_SUPPORT. I think this was done to avoid a link failure. It's also possible that this is a mistake and just did not get caught in review. Arnd 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=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,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 0AC64C4740A for ; Mon, 9 Sep 2019 15:09:14 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 D2AB120863 for ; Mon, 9 Sep 2019 15:09:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="tRICGz+a" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D2AB120863 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=w9GuzH8zUOj3Ch6RyuN/oAaW0Dhdh4YT/lmmvsQywV4=; b=tRICGz+accCRFK 21IyuSmdBA1nqgC5gV9zxBF2pQQ8+pk4hnbCA48U1AMUrWMefpWZKXcVFGhVzxrIZVA7VaCjDyAt3 vgsFiazJu/9m7PuFQKVyIjWGXeGG5Q2pDObl7mrQ19euzVzipHjloBB9dNcLXuo1ETniDG+38XKDy TTUMb2jNO3dsaXkuGw5us4dLLsf6e4g6nL3zXoKxKVc9ZSvu9vHDxy6RhthqaHVbgLNzcZ+nt7loz CJSLRKhV5m+iAmTo4CQZLo3Zb5ibMlVkgRtkDMCVbokX8t1l2lHnNrlz93rs6fTwrkC19sL2bNFZz Pj0MHky7oB8typiyU8DQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1i7LHy-0004Ye-PS; Mon, 09 Sep 2019 15:09:10 +0000 Received: from mail-qk1-f195.google.com ([209.85.222.195]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1i7LHv-0004YA-Is for linux-arm-kernel@lists.infradead.org; Mon, 09 Sep 2019 15:09:08 +0000 Received: by mail-qk1-f195.google.com with SMTP id x134so13430648qkb.0 for ; Mon, 09 Sep 2019 08:09:07 -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=BRd75HfAMA/RM+2IUVcveN8rNVBoGEbq4cpvizDx7NM=; b=uMoGP+6agxsMTuIRKbnfm9ubVYy6HLIWv31A3c4aA6RDleXwX8cmDVZBna6SFJR4GP OnBEzZKWv4vgofQIzAZptwoWYQcf+4hAThusIlyQYc+E2GtWWpCTYsLEA7GWJFtZIZA4 kRSLNbKUeYwUjqUGzjOuZGAMPNdQ9XuXWS1PObURMrS4a+gCuNnNSWirRMNqgdfbrcKv HB5LLxuJLGVOlabDRLLe5Ri65/ieJYcWy4EENl3B+7Oj1wwE0SQK5tTjLEBbT1uCQjzZ xGhTa6cgx/MkqLne7oSv1cYl6B+64oLd1BPstte/XO+V2o1p6xmU6mFNSsd4ENX6nM+6 RovQ== X-Gm-Message-State: APjAAAXIlH0YrtlZekrFUnllWuA4HKf6IQVCF/Z4UEYPGIkc6SVYdC7S k8zZmFUp/eJU5uugKYuE+RYr475UxhyG/DeQshEmW3tM X-Google-Smtp-Source: APXvYqyixTPG+CFUK1hDkQTl3ReqfwNBD/A6zafQDgbntwdHXHwkh+RNO8Na4ISyGRsSqSCfU/vXAgp7FItNdTdN170= X-Received: by 2002:ae9:ee06:: with SMTP id i6mr3208112qkg.3.1568041746371; Mon, 09 Sep 2019 08:09:06 -0700 (PDT) MIME-Version: 1.0 References: <1568020220-7758-1-git-send-email-talel@amazon.com> <1568020220-7758-4-git-send-email-talel@amazon.com> <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> In-Reply-To: <0d36f94d-596f-0ec7-6951-b097b5ee0d2d@amazon.com> From: Arnd Bergmann Date: Mon, 9 Sep 2019 17:08:50 +0200 Message-ID: Subject: Re: [PATCH 3/3] arm64: alpine: select AL_POS To: "Shenhar, Talel" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190909_080907_626219_9E0DA09B X-CRM114-Status: GOOD ( 14.83 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , mjourdan@baylibre.com, Catalin Marinas , Linus Walleij , "linux-kernel@vger.kernel.org" , jonnyc@amazon.com, Mauro Carvalho Chehab , ronenk@amazon.com, Will Deacon , Benjamin Herrenschmidt , DTML , Maxime Ripard , Rob Herring , Santosh Shilimkar , Thomas Gleixner , hanochu@amazon.com, Linux ARM , barakw@amazon.com, hhhawa@amazon.com, gregkh , paul.kocialkowski@bootlin.com, Patrick Venture , Olof Johansson , David Miller , David Woodhouse Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Sep 9, 2019 at 3:59 PM Shenhar, Talel wrote: > On 9/9/2019 4:45 PM, Arnd Bergmann wrote: > > Its not that something will get broken. its error event detector for POS > events which allows seeing bad accesses to registers. > > What is the general rule of which configs to put under select and which > under defconfig? > > I was thinking that "general" SoC support is good under select - those > things that we always want. I generally want as little as possible to be selected, basically only things that are required for linking the kernel and booting it without potentially destroying the hardware. In particular, I want most drivers to be enabled as loadable modules if possible. When you have general-purpose distributions support your platform, there is no need to have this module built-in while running on a different chip, even if you always want to load the module when it's running on yours. > And specific features, e.g. RAID support or features that supported only > on specific HW shall go under defconfig. > > Similar, I see ARCH_LAYERSCAPE selecting EDAC_SUPPORT. I think this was done to avoid a link failure. It's also possible that this is a mistake and just did not get caught in review. Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel