From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755520AbaEOTZM (ORCPT ); Thu, 15 May 2014 15:25:12 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:42805 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752316AbaEOTZI (ORCPT ); Thu, 15 May 2014 15:25:08 -0400 Message-ID: <5375148E.6040905@wwwdotorg.org> Date: Thu, 15 May 2014 13:25:02 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andrew Bresticker , linux-tegra@vger.kernel.org CC: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Thierry Reding , Russell King , Peter De Schrijver , Prashant Gaikwad , Mike Turquette , Kishon Vijay Abraham I , Greg Kroah-Hartman , Mathias Nyman , Grant Likely , Randy Dunlap Subject: Re: [RFC PATCH 08/10] ARM: tegra124: Bind CAR to syscon device References: <1400113986-339-1-git-send-email-abrestic@chromium.org> <1400113986-339-9-git-send-email-abrestic@chromium.org> In-Reply-To: <1400113986-339-9-git-send-email-abrestic@chromium.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/14/2014 06:33 PM, Andrew Bresticker wrote: > The XUSB PHY driver will be accessing the CAR registers through the > syscon interface. I very strongly don't want to use the syscon concept on Tegra. Instead, I want only the CAR driver touching the CAR registers. If other drivers need some CAR registers manipulated, that should happen by that other driver calling some explicit semantic API in the CAR driver to do so. Take a look at how the Tegra SMMU and Tegra AHB driver communicate for an example.