Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751763AbdFTQK6 (ORCPT ); Tue, 20 Jun 2017 12:10:58 -0400 Received: from mail-io0-f170.google.com ([209.85.223.170]:34210 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052AbdFTQKz (ORCPT ); Tue, 20 Jun 2017 12:10:55 -0400 MIME-Version: 1.0 In-Reply-To: References: <1491895862-7952-1-git-send-email-richard.leitner@skidata.com> <0a29de1a-2635-2bb8-808a-7b9a0197921a@skidata.com> <6b92d0af00024549a0d22dda039780dd@bowex36d.micron.com> From: Linus Walleij Date: Tue, 20 Jun 2017 18:10:53 +0200 Message-ID: Subject: Re: [EXT] Re: [PATCH v2] mmc: core: add mmc-card hardware reset enable support To: Richard Leitner Cc: "Luca Porzio (lporzio)" , Ulf Hansson , Bart Van Assche , Rob Herring , Mark Rutland , Shawn Lin , Adrian Hunter , Jaehoon Chung , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , Richard Leitner Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 406 Lines: 12 On Tue, Jun 20, 2017 at 12:24 PM, Richard Leitner wrote: > Should we then add a warning/info message to the kernel if we have a > reset gpio configured in the DT, but the eMMC hasn't this OTP bit set? That makes a lot of sense. Because the situation is ambigous. We provide the hardware to reset the card, but the card says it does not accept a reset. Yours, Linus Walleij