Re: [PATCH] remoteproc: qcom: Introduce Hexagon V5 based WCSS driver

From: Vinod
Date: Thu Jun 07 2018 - 04:44:00 EST


On 06-06-18, 21:24, Bjorn Andersson wrote:
> On Wed 06 Jun 21:11 PDT 2018, Vinod wrote:
>
> > So, wouldn't Kconfig syntax something like where we say:
> > M if RPMSG_QCOM_GLINK_SMEM=m
> > bool if RPMSG_QCOM_GLINK_SMEM=y
> >
>
> If we ignore SMD for a while we have the following combinations:
>
> glink/wcss
> y y - valid
> y m - valid
> y n - valid
> m y - link failure (invalid)
> m m - valid
> m n - valid
> n y - valid (platform uses wcss, but not glink)
> n m - valid (-----"-----)
> n n - valid
>
> So to distill this we have the two valid cases:
> module/no if RPMSG_QCOM_GLINK_SMEM=m
> yes/module/no if RPMSG_QCOM_GLINK_SMEM=y
>
> and the way you express that in Kconfig is the somewhat awkward
>
> depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n

Understood now :) Yes it is awkward..

Btw we seem to have issue with link fail here when glink is m and wcss
is y. Why don't we see link fail for glink being n? Yes I understand that
platform uses wcss but am curious how that works out :)

Thanks
--
~Vinod