From: Amitkumar Karwar <akarwar@marvell.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Cathy Luo" <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Wei-Ning Huang <wnhuang@chromium.org>,
Xinming Hu <huxm@marvell.com>
Subject: RE: [PATCH] mwifiex: parse device tree node for PCIe
Date: Thu, 29 Sep 2016 13:58:23 +0000 [thread overview]
Message-ID: <0fb142f41f764496bc1242507717f0f7@SC-EXCH04.marvell.com> (raw)
In-Reply-To: <20160919212753.GA16598@rob-hp-laptop>
Hi Rob,
> From: Rob Herring [mailto:robh@kernel.org]
> Sent: Tuesday, September 20, 2016 2:58 AM
> To: Amitkumar Karwar
> Cc: linux-wireless@vger.kernel.org; Cathy Luo; Nishant Sarmukadam;
> devicetree@vger.kernel.org; Wei-Ning Huang; Xinming Hu
> Subject: Re: [PATCH] mwifiex: parse device tree node for PCIe
>
> On Fri, Sep 09, 2016 at 08:47:34PM +0530, Amitkumar Karwar wrote:
> > From: Xinming Hu <huxm@marvell.com>
> >
> > This patch derives device tree node from pcie bus layer framework.
> > Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
> > marvell-8xxx.txt) to accomodate PCIe changes.
> >
> > Signed-off-by: Xinming Hu <huxm@marvell.com>
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > ---
> > .../bindings/net/wireless/marvell-8xxx.txt | 64
> ++++++++++++++++++++++
> > .../bindings/net/wireless/marvell-sd8xxx.txt | 63 -------------
> --------
>
> Resend using -M option so I do have to figure out if you added 1 line or
> changed a bunch.
>
> > drivers/net/wireless/marvell/mwifiex/pcie.c | 19 +++++++
> > drivers/net/wireless/marvell/mwifiex/sta_cmd.c | 3 +-
> > 4 files changed, 85 insertions(+), 64 deletions(-) create mode
> > 100644 Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt
> > delete mode 100644
> > Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt
> >
> > diff --git
> > a/Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt
> > b/Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt
> > new file mode 100644
> > index 0000000..a8a95aa
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt
> > @@ -0,0 +1,64 @@
> > +Marvell 8897/8997 (sd8897/sd8997/pcie8997) SDIO/PCIE devices
> > +------
> > +
> > +This node provides properties for controlling the marvell sdio/pcie
> wireless device.
> > +The node is expected to be specified as a child node to the SDIO/PCIE
> > +controller that connects the device to the system.
> > +
> > +Required properties:
> > +
> > + - compatible : should be one of the following:
> > + * "marvell,sd8897"
> > + * "marvell,sd8997"
> > + * "marvell,pcie8997"
>
> PCIe uses vendor and product IDs for compatible strings. Please read the
> OF PCI bus bindings doc.
>
Thanks for review. I have submitted updated version(V3) with this change.
Regards,
Amitkumar Karwar
prev parent reply other threads:[~2016-09-29 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 15:17 [PATCH] mwifiex: parse device tree node for PCIe Amitkumar Karwar
2016-09-19 21:27 ` Rob Herring
2016-09-29 13:58 ` Amitkumar Karwar [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=0fb142f41f764496bc1242507717f0f7@SC-EXCH04.marvell.com \
--to=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=robh@kernel.org \
--cc=wnhuang@chromium.org \
/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