Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5494965ybi; Tue, 4 Jun 2019 07:30:53 -0700 (PDT) X-Google-Smtp-Source: APXvYqxWR5mi9C9TuhGID4BnR5nhPyySx1bQUxPwKB1cvmqmW75j+VSr4jADPlVdieG+ircKv93l X-Received: by 2002:a17:902:26c:: with SMTP id 99mr38021841plc.215.1559658653270; Tue, 04 Jun 2019 07:30:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559658653; cv=none; d=google.com; s=arc-20160816; b=U8jIgjSp/SEt3Tff3HyRDwgJjEjWoMeJj7LwlKhxO/WVWxYBrxANZOv5BrTCO3iQbm D+2i4IERNjT3u3FlmB7hCMIWTzx5LV8aObQizR4cvh2/+KMusTwzRRjXevnVBLMmsjjD jUdtWvSc/+J9HfSlyySzH+GJduBOxMieqSPeG3safVuCkPy1hhaIn/jcH5CuLWVY1GMb rJmI/o8miQaVUlx24jRif5fFN3izbBxnvopvA8Vl6dM5h7VuR5huMQQ3kqhK4t0HADaQ NyynG8W0K9PUHtrsQgJR0u6Vce/kq/7CrJk1WjepBbRUjiphs39/4TVTHX0+jhqRHJio DeuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=XxlFFiNkPgwViRGWwayzugUZoFxggdshl8Sxry8bl/c=; b=cakkfSIYgJ3AMY6iDlVv9v1aDP7W6JB29ikdCHrINmuWEGQhtg950tAG0ISS9yANIt +yBH6IKIpihndFhFOowIAKPWvLuoJPgSeZRrYBCGj8Ke73+Q+diGAXyrf3f+pHimjQ8W rQw7J/7uYQauFxu0+ozrILnodh9nCT9gXoq3BybELMo6AUlJWQMxyMDv+NE7NNAlBpEa BtTOm8oeKE2v5Oim25ov7LpnuWCA/DcAp/oizkH2DAcfzl1/qvlZtjnaEI//reQ3zjjk d5ca/C/3pGL5HkFhCj18l3DRdc3XzmxBJKrSSwKxvnjf/Yr9MI3jdDgA/YJrEBwkIw9d wOzQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="mGq/RcvU"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g129si23641736pfb.181.2019.06.04.07.30.34; Tue, 04 Jun 2019 07:30:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="mGq/RcvU"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727757AbfFDO2l (ORCPT + 99 others); Tue, 4 Jun 2019 10:28:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:42988 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727169AbfFDO2k (ORCPT ); Tue, 4 Jun 2019 10:28:40 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9E4AD2498F; Tue, 4 Jun 2019 14:28:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559658520; bh=O7gbnZkk6GvrbVTl6bI9UPon+W+udWxZvh/zYblS/1E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mGq/RcvUMLPKU/cWsDJ4IfF8EVqouENT3sn2nQ+9c7sYPAiCQmC0RxTwbc/mjHy5d 83v105+qfyjymk+w+8cgUQ1eZuSbkvJHDCja+sAdzS+Dn8gRWNndYNjSvj0jOlm0HG emi4ss3C/xcI9UBK1CIYD1M/pARhXG19y7/N8KP4= Date: Tue, 4 Jun 2019 16:28:37 +0200 From: Greg KH To: Richard Gong Cc: robh+dt@kernel.org, mark.rutland@arm.com, dinguyen@kernel.org, atull@kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, sen.li@intel.com, Richard Gong Subject: Re: A potential broken at platform driver? Message-ID: <20190604142837.GB28355@kroah.com> References: <1559074833-1325-1-git-send-email-richard.gong@linux.intel.com> <1559074833-1325-3-git-send-email-richard.gong@linux.intel.com> <20190528232224.GA29225@kroah.com> <1e3b5447-b776-f929-bca6-306f90ac0856@linux.intel.com> <20190603180255.GA18054@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 03, 2019 at 06:08:37PM -0500, Richard Gong wrote: > Hi Greg, > > On 6/3/19 1:02 PM, Greg KH wrote: > > On Mon, Jun 03, 2019 at 10:57:18AM -0500, Richard Gong wrote: > > > > > > Hi Greg, > > > > > > Following your suggestion, I replaced devm_device_add_groups() with .group = > > > rus_groups in my version #4 submission. But I found out that RSU driver > > > outputs the garbage data if I use .group = rsu_groups. > > > > What is "garbage"? > I mean incorrect status info. > > > > > > To make RSU driver work properly, I have to revert the change at version #4 > > > and use devm_device_add_groups() again. Sorry, I didn't catch this problem > > > early. > > > > > > I did some debug & below are captured log, you can see priv pointer get > > > messed at current_image_show(). I am not sure if something related to > > > platform driver work properly. I attach my debug patch in this mail. > > > > > > 1. Using .groups = rsu_groups, > > > > > > [ 1.191115] *** rsu_status_callback: > > > [ 1.194782] res->a1=2000000 > > > [ 1.197588] res->a1=0 > > > [ 1.199865] res->a2=0 > > > [ 1.202150] res->a3=0 > > > [ 1.204433] priv=0xffff80007aa28e80 > > > [ 1.207933] version=0, state=0, current_image=2000000, fail_image=0, > > > error_location=0, error_details=0 > > > [ 1.217249] *** stratix10_rsu_probe: priv=0xffff80007aa28e80 > > > root@stratix10:/sys/bus/platform/drivers/stratix10-rsu# cat current_image > > > [ 38.849341] *** current_image_show: priv=0xffff80007aa28d00 > > > ... output garbage data > > > priv pointer got changed > > > > I don't understand this, sorry. Are you sure you are actually using the > > correct pointer to your device? > > > I think so. > > The dev pointer at current_image_show() should points to RSU device, but it > seems point to driver_private if I use .group = rsU_groups. As a result I > can't get the priv pointer properly at current_image_show(). It points to the driver kobject, not the device kobject. So that's the issue here. See the patch that I just posted for a potential fix for this. thanks, greg k-h