[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180917010820.GB3900@dell>
Date: Mon, 17 Sep 2018 02:08:20 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: robh+dt@...nel.org, broonie@...nel.org, mark.rutland@....com,
lgirdwood@...il.com, bgoswami@...eaurora.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
vkoul@...nel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH v3 02/13] mfd: wcd9335: add support to wcd9335 core
On Wed, 12 Sep 2018, Srinivas Kandagatla wrote:
>
> > >
> > > There are two parts for device to be ready to talk at bus level:
> > > 1> power up and reset,
> > > 2> enumerate and assign a logical address by the slimbus controller.
> > >
> > > First part as you said is already done in probe.
> > > When second part happens when status callback is invoked, that is when the
> > > slimdevice is ready for any kind of communication at bus level.
> >
> > I see. I still think it's hacky to conduct start-up procedures when
> > all the SS requested was status. Perhaps it needs a new API call
> > init()?
>
> When we added these callbacks the purpose of this was to allow drivers to do
> specific setup/teardown.
>
> AFIAU,
What does that mean?
> even-though if we add init(), SLIMbus would still call it just before
> or after status which to me is redundant ATM.
> Its up to slim driver what it exactly whats to do with status, in some cases
> this can involve setting up the device.
If you say so! ;)
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists