From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S969315AbdAEP0z (ORCPT ); Thu, 5 Jan 2017 10:26:55 -0500 Received: from mail-qk0-f173.google.com ([209.85.220.173]:35717 "EHLO mail-qk0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967153AbdAEP0q (ORCPT ); Thu, 5 Jan 2017 10:26:46 -0500 MIME-Version: 1.0 In-Reply-To: <20170104135644.GA29212@leverpostej> References: <20161117183541.8588-1-bigeasy@linutronix.de> <20161117183541.8588-16-bigeasy@linutronix.de> <20170102150015.GJ14217@n2100.armlinux.org.uk> <20170103093335.GA5605@leverpostej> <20170104135644.GA29212@leverpostej> From: Linus Walleij Date: Thu, 5 Jan 2017 16:26:45 +0100 Message-ID: Subject: Re: [PATCH 15/20] ARM/hw_breakpoint: Convert to hotplug state machine To: Mark Rutland Cc: Will Deacon , Sebastian Andrzej Siewior , rt@linuxtronix.de, Russell King - ARM Linux , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Stephen Boyd , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 4, 2017 at 2:56 PM, Mark Rutland wrote: > I've just reproduced this locally on my dragonboard APQ8060. Sweet! > It looks like the write_wb_reg() call that's exploding is from > get_max_wp_len(), which we call immediately after registering the > dbg_reset_online callback. Clearing DBGPRSR.SPD before the write_wb_reg() hides > the problem, so I suspect we're seeing the issue I mentioned above -- it just > so happens that we go idle in a new place. > > The below hack allows boot to continue, but is not a real fix. I'm not > immediately sure what to do. Me neither. But Will's suggestion to simply blacklist this chip might be best. > Linus, I wasn't able to get ethernet working. Do I need anything on top > of v4.10-rc2 && multi_v7_defconfig? I haven't tried it with multi_v7 but I should probably try that and patch up the defconfigs, those are probably the root of the problem. I do this on top of qcom_defconfig: scripts/config --file .config \ --enable QCOM_EBI2 \ --enable ETHERNET \ --enable NET_VENDOR_SMSC \ --enable SMSC911X Maybe you are missing the EBI2 config? Yours, Linus Walleij