linux-kernel - How the registration of rpmsg devices should be done?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEvN+1i8O-GhJ1s9mpeG1WvX850AjezCHgdsjQop6syP3pJPhQ@mail.gmail.com>
Date:	Wed, 4 Jul 2012 16:26:48 +0800
From:	Tzu-Jung Lee <roylee17@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	ohad@...ery.com
Subject: How the registration of rpmsg devices should be done?

Hi,

I working on the IPC functionality on our SoC and is looking into the
rpmsg & remoteproc framework of inux v3.4.

However, a piece of code seems to be missing in the
drivers/rpmsg/virtio_rpmsg_bus.c linux-v3.4 (compared to the
omap/linux-kernel-3.0)

@@ -898,82 +667,91 @@ static int rpmsg_probe(struct virtio_device *vdev)

+       /* look for platform-specific static channels */
+       vdev->config->get(vdev, VPROC_STATIC_CHANNELS, &ch, sizeof(ch));
+
+       for (i = 0; ch && ch[i].name[0]; i++)
+               rpmsg_create_channel(vrp, &ch[i]);

Since rpmsg_create_channel() is static and internal to rpmsg module,
I'm wondering how the registration of rpmsg device should be done?

Thanks,
Roy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/