From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH v3 03/23] serial: omap: don't access the platform_device Date: Fri, 24 Aug 2012 12:07:33 -0700 Message-ID: <20120824190733.GQ11011@atomide.com> References: <1345717983-18179-1-git-send-email-balbi@ti.com> <1345717983-18179-4-git-send-email-balbi@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1345717983-18179-4-git-send-email-balbi@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Felipe Balbi Cc: Kevin Hilman , Linux Kernel Mailing List , Santosh Shilimkar , linux-serial@vger.kernel.org, Sourav Poddar , Linux OMAP Mailing List , Shubhrajyoti Datta , Linux ARM Kernel Mailing List , alan@linux.intel.com List-Id: linux-omap@vger.kernel.org * Felipe Balbi [120823 03:37]: > The driver doesn't need to know about its platform_device. > > Everything the driver needs can be done through the > struct device pointer. In case we need to use the > OMAP-specific PM function pointers, those can make > sure to find the device's platform_device pointer > so they can find the struct omap_device through > pdev->archdata field. > > Tested-by: Shubhrajyoti D > Acked-by: Santosh Shilimkar > Signed-off-by: Felipe Balbi Acked-by: Tony Lindgren From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Fri, 24 Aug 2012 12:07:33 -0700 Subject: [PATCH v3 03/23] serial: omap: don't access the platform_device In-Reply-To: <1345717983-18179-4-git-send-email-balbi@ti.com> References: <1345717983-18179-1-git-send-email-balbi@ti.com> <1345717983-18179-4-git-send-email-balbi@ti.com> Message-ID: <20120824190733.GQ11011@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Felipe Balbi [120823 03:37]: > The driver doesn't need to know about its platform_device. > > Everything the driver needs can be done through the > struct device pointer. In case we need to use the > OMAP-specific PM function pointers, those can make > sure to find the device's platform_device pointer > so they can find the struct omap_device through > pdev->archdata field. > > Tested-by: Shubhrajyoti D > Acked-by: Santosh Shilimkar > Signed-off-by: Felipe Balbi Acked-by: Tony Lindgren From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760222Ab2HXV0H (ORCPT ); Fri, 24 Aug 2012 17:26:07 -0400 Received: from mho-04-ewr.mailhop.org ([204.13.248.74]:42063 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752997Ab2HXV0D (ORCPT ); Fri, 24 Aug 2012 17:26:03 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 98.234.237.12 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+UfCLLAtIiZ2UoB7n4akPm Date: Fri, 24 Aug 2012 12:07:33 -0700 From: Tony Lindgren To: Felipe Balbi Cc: alan@linux.intel.com, Kevin Hilman , Linux OMAP Mailing List , Linux ARM Kernel Mailing List , linux-serial@vger.kernel.org, Linux Kernel Mailing List , Santosh Shilimkar , Shubhrajyoti Datta , Sourav Poddar Subject: Re: [PATCH v3 03/23] serial: omap: don't access the platform_device Message-ID: <20120824190733.GQ11011@atomide.com> References: <1345717983-18179-1-git-send-email-balbi@ti.com> <1345717983-18179-4-git-send-email-balbi@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1345717983-18179-4-git-send-email-balbi@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Felipe Balbi [120823 03:37]: > The driver doesn't need to know about its platform_device. > > Everything the driver needs can be done through the > struct device pointer. In case we need to use the > OMAP-specific PM function pointers, those can make > sure to find the device's platform_device pointer > so they can find the struct omap_device through > pdev->archdata field. > > Tested-by: Shubhrajyoti D > Acked-by: Santosh Shilimkar > Signed-off-by: Felipe Balbi Acked-by: Tony Lindgren