From: German Rivera <German.Rivera@freescale.com>
To: Alexander Graf <agraf@suse.de>, <gregkh@linuxfoundation.org>,
<arnd@arndb.de>, <linux-kernel@vger.kernel.org>
Cc: <stuart.yoder@freescale.com>, <Kim.Phillips@freescale.com>,
<scottwood@freescale.com>, <bhamciu1@freescale.com>,
<R89243@freescale.com>, <Geoff.Thorpe@freescale.com>,
<bhupesh.sharma@freescale.com>, <nir.erez@freescale.com>,
<richard.schmitt@freescale.com>
Subject: Re: [PATCH 3/3 v3] drivers/bus: Device driver for FSL-MC DPRC devices
Date: Thu, 13 Nov 2014 11:37:54 -0600 [thread overview]
Message-ID: <5464EC72.7040501@freescale.com> (raw)
In-Reply-To: <545B7CD5.8090802@suse.de>
On 11/06/2014 07:51 AM, Alexander Graf wrote:
>
>
> On 04.10.14 15:23, J. German Rivera wrote:
>> From: "J. German Rivera" <German.Rivera@freescale.com>
>>
>> A DPRC (Data Path Resource Container) is an isolation device
>> that contains a set of DPAA networking devices to be
>> assigned to an isolation domain (e.g., a virtual machine).
>>
>> Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
>> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
>> ---
>> Changes in v3:
>> - Addressed comments from Kim Phillips:
>> * Renamed files:
>> drivers/bus/fsl-mc/fsl_mc_dprc.c -> drivers/bus/fsl-mc/dprc-driver.c
>>
>> - Addressed comments from Timur Tabi:
>> * Changed dprc_scan_container() to just return dprc_scan_objects()
>> * Changed all functions that had goto out/error when no common cleanup
>> was done, to just have multiple return points.
>> * Replaced error cleanup boolean flags with multiple exit points.
>> * REmoved __must_chewck from dprc_scan_*() functions
>>
>> Changes in v2:
>> - Addressed comments from Kim Phillips:
>> * Fix warning in drivers/bus/fsl-mc/fsl_mc_dprc.c:173
>> * Fixed linker errors when MC bus driver built as module
>>
>> drivers/bus/fsl-mc/Makefile | 3 +-
>> drivers/bus/fsl-mc/dprc-driver.c | 383 ++++++++++++++++++++++++++++++++++++++
>> drivers/bus/fsl-mc/mc-bus.c | 8 +
>> include/linux/fsl/mc-private.h | 10 +
>> 4 files changed, 403 insertions(+), 1 deletion(-)
>> create mode 100644 drivers/bus/fsl-mc/dprc-driver.c
>>
>> diff --git a/drivers/bus/fsl-mc/Makefile b/drivers/bus/fsl-mc/Makefile
>> index decd339..424e58e 100644
>> --- a/drivers/bus/fsl-mc/Makefile
>> +++ b/drivers/bus/fsl-mc/Makefile
>> @@ -10,5 +10,6 @@ obj-$(CONFIG_FSL_MC_BUS) += mc-bus-driver.o
>> mc-bus-driver-objs := mc-bus.o \
>> mc-sys.o \
>> dprc.o \
>> - dpmng.o
>> + dpmng.o \
>> + dprc-driver.o
>>
>> diff --git a/drivers/bus/fsl-mc/dprc-driver.c b/drivers/bus/fsl-mc/dprc-driver.c
>> new file mode 100644
>> index 0000000..8be6a2a
>> --- /dev/null
>> +++ b/drivers/bus/fsl-mc/dprc-driver.c
>> @@ -0,0 +1,383 @@
>> +/*
>> + * Freescale daata path resource container (DPRC) driver
>
> daata? ;)
>
Fixed.
> Is there any way I can play with this bus? How far do I get with only
> these 3 patches applied today?
>
With these three patches applied you will be able to see the fsl-mc bus
added in sysfs and the device present in the root DPRC.
Also, since this patch series only contains one MC object driver
(the driver for DPRC objects), you will be able so see that
driver under the fsl-mc bus. Below is a fragment of console
output with an example to illustrate this:
root@ls2085a-simu:~# find /sys/bus/fsl-mc/
/sys/bus/fsl-mc/
/sys/bus/fsl-mc/devices
/sys/bus/fsl-mc/devices/dpbp.1
/sys/bus/fsl-mc/devices/dpio.1
/sys/bus/fsl-mc/devices/dpni.1
/sys/bus/fsl-mc/devices/dprc.1
/sys/bus/fsl-mc/drivers
/sys/bus/fsl-mc/drivers/fsl_mc_dprc
/sys/bus/fsl-mc/drivers/fsl_mc_dprc/bind
/sys/bus/fsl-mc/drivers/fsl_mc_dprc/dprc.1
/sys/bus/fsl-mc/drivers/fsl_mc_dprc/uevent
/sys/bus/fsl-mc/drivers/fsl_mc_dprc/unbind
/sys/bus/fsl-mc/uevent
/sys/bus/fsl-mc/drivers_probe
/sys/bus/fsl-mc/drivers_autoprobe
root@ls2085a-simu:~# ls -l /sys/bus/fsl-mc/devices/dprc.1/
drwxr-xr-x 3 root root 0 Jan 1 1970 dpbp.1
drwxr-xr-x 3 root root 0 Jan 1 1970 dpio.1
drwxr-xr-x 3 root root 0 Jan 1 1970 dpni.1
lrwxrwxrwx 1 root root 0 Nov 7 20:38 driver ->
../../../bus/fsl-mc/drivers/fsl_mc_dprc
drwxr-xr-x 2 root root 0 Nov 7 20:38 power
lrwxrwxrwx 1 root root 0 Jan 1 1970 subsystem ->
../../../bus/fsl-mc
-rw-r--r-- 1 root root 4096 Jan 1 1970 uevent
Thanks,
German
>
> Alex
>
prev parent reply other threads:[~2014-11-13 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:23 [PATCH 0/3 v3] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2014-10-04 13:23 ` [PATCH 1/3 v3] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-11-06 13:49 ` Alexander Graf
2014-11-12 0:49 ` German Rivera
2014-10-04 13:23 ` [PATCH 2/3 v3] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-11-06 13:50 ` Alexander Graf
2014-11-12 2:01 ` German Rivera
2014-10-04 13:23 ` [PATCH 3/3 v3] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-10-05 14:53 ` Timur Tabi
2014-10-06 14:48 ` German Rivera
2014-11-10 4:37 ` Timur Tabi
2014-11-06 13:51 ` Alexander Graf
2014-11-13 17:37 ` German Rivera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5464EC72.7040501@freescale.com \
--to=german.rivera@freescale.com \
--cc=Geoff.Thorpe@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox