From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757515AbbGGO3O (ORCPT ); Tue, 7 Jul 2015 10:29:14 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:34814 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756815AbbGGO2W (ORCPT ); Tue, 7 Jul 2015 10:28:22 -0400 From: Roger Quadros To: , , CC: , , , , Roger Quadros Subject: [PATCH 0/2] ARM: dra7: fix DCAN glitch Date: Tue, 7 Jul 2015 17:27:55 +0300 Message-ID: <1436279277-3386-1-git-send-email-rogerq@ti.com> X-Mailer: git-send-email 2.1.4 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, If "default" pins are active for CAN then there is a slight window during boot when CAN pins are in active mode and can affect DRA7 CAN stability. This is because device core automatically selects "default" before probe. These patches change "default" pins to inactive and adds a new "active" pin state so that we don't encounter the glitch mentioned above. cheers, -roger J.D. Schroeder (1): net: can: c_can: Fix default pinmux glitch at init Roger Quadros (1): ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux arch/arm/boot/dts/dra7-evm.dts | 5 +++-- arch/arm/boot/dts/dra72-evm.dts | 5 +++-- drivers/net/can/c_can/c_can.c | 13 ++++++++++++- 3 files changed, 18 insertions(+), 5 deletions(-) -- 2.1.4