[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01bb6d9c1c7f4419b2d88051b8e811f4@SC-EXCH04.marvell.com>
Date: Thu, 9 Jun 2016 13:51:45 +0000
From: Amitkumar Karwar <akarwar@...vell.com>
To: Julian Calaby <julian.calaby@...il.com>,
Javier Martinez Canillas <javier@....samsung.com>,
Xinming Hu <huxm@...vell.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kalle Valo <kvalo@...eaurora.org>,
netdev <netdev@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
Nishant Sarmukadam <nishants@...vell.com>
Subject: RE: [PATCH 7/8] mwifiex: don't print an error if an optional DT
property is missing
> From: Julian Calaby [mailto:julian.calaby@...il.com]
> Sent: Thursday, June 02, 2016 4:44 AM
> To: Javier Martinez Canillas; Xinming Hu
> Cc: linux-kernel@...r.kernel.org; Amitkumar Karwar; Kalle Valo; netdev;
> linux-wireless; Nishant Sarmukadam
> Subject: Re: [PATCH 7/8] mwifiex: don't print an error if an optional DT
> property is missing
>
> Hi Javier,
>
> On Wed, Jun 1, 2016 at 11:51 PM, Javier Martinez Canillas
> <javier@....samsung.com> wrote:
> > Hello Julian,
> >
> > Thanks a lot for your feedback and reviews.
> >
> > On 06/01/2016 12:20 AM, Julian Calaby wrote:
> >> Hi All,
> >>
> >> On Sat, May 28, 2016 at 12:18 AM, Javier Martinez Canillas
> >> <javier@....samsung.com> wrote:
> >>> The
> >>> Documentation/devicetree/bindings/net/wireless/marvell-sd8xxx.txt DT
> >>> binding document say that the "interrupts" property in the child
> node is optional. So the property being missed shouldn't be treated as
> an error.
> >>
> >> Have you checked whether it is truly optional? I.e. nothing else
> >> breaks if this property isn't set?
> >>
> >
> > That's what the DT binding says and the IRQ is only used as a wakeup
> > source during system suspend, it is not used during runtime. And that
> > is why the
> > mwifiex_sdio_probe_of() function does not fail if the IRQ is missing.
>
> Awesome, that's what I wanted to know.
>
> > Now, I just got to that conclusion by reading the binding docs, the
> > message in the commits that introduced this and the driver code.
> > Xinming Hu should comment on how critical this feature is for systems
> that needs to be wakeup.
>
> Xinming, could you review this also?
>
Yes. IRQ is the optional parameter. System has a flexibility to not use it, but it still can configure other device tree parameters. The patch looks good.
Regards,
Amitkumar
Powered by blists - more mailing lists