[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140425141551.GL5546@joshc.qualcomm.com>
Date: Fri, 25 Apr 2014 09:15:51 -0500
From: Josh Cartwright <joshc@...eaurora.org>
To: "Ivan T. Ivanov" <iivanov@...sol.com>
Cc: Courtney Cavin <courtney.cavin@...ymobile.com>,
Josh Cartwright <joshc@...eaurora.org>,
Rob Herring <robherring2@...il.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
linux-arm-msm <linux-arm-msm@...r.kernel.org>
Subject: Re: [RFC PATCH] mfd: pm8x41: Naive function devices registration
On Fri, Apr 25, 2014 at 03:32:51PM +0300, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov" <iivanov@...sol.com>
>
> Currently functions that exist in both the controller at the
> same address offset can not be specified with the same names.
The terminology here is a bit confusing. When I read "controller", I
hear "SPMI controller", but this is really not a limitation of the SPMI
core, but rather a limitation of of_platform_populate() used by this
particular SPMI slave MFD driver.
> Adding Unique Slave ID device address to prefix function
> device names fixes this.
>
> Function devices are SPMI devices, so register them on
> SPMI bus.
This is a step backwards. The PMIC functions are not individually
addressable SPMI slaves, and as such should not be represented as
independent devices to the SPMI core.
They really are subfunctions of a particular SPMI slave, and should be
modeled as children of that slave device. With this driver, we've
chosen to model the child devices as platform devices, but it could
also be a separate bus type.
Josh
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists