On Thu, Oct 5, 2017 at 8:14 AM, Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> wrote: > On Sun 01 Oct 21:18 PDT 2017, Anup Patel wrote: > >> Currently, RPMSG_VIRTIO can only be enabled if some other kconfig >> option selects it. This does not allow it to be enabled for >> virtualized systems where Virtio RPMSG is available over Virtio >> MMIO or PCI transport. >> >> This patch updates RPMSG_VIRTIO kconfig option so that we can >> enable the VirtIO RPMSG driver via menuconfig or defconfig. >> >> Signed-off-by: Anup Patel <anup@xxxxxxxxxxxxxx> >> --- > > This part looks good (and really I think this is the right thing to do). > But turning RPMSG_VIRTIO into a user selectable item makes it invalid to > "select RPMSG_VIRTIO" from drivers/remoteproc/Kconfig. > > Can you please as part of this change remove those selects and as a > separate patch add CONFIG_RPMSG_VIRTIO=m to > arch/arm/configs/multi_v7_defconfig? Sure, I will update the patch as-per your suggestion and also send separate patch to add CONFIG_RPMSG_VIRTIO=m in arch/arm/configs/multi_v7_defconfig. Regards, Anup -- To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
