Kevin Cameron wrote: > David Miller wrote: >>> I didn't get any feedback on on the connect module placement issue - >>> >>> http://www.verilog.org/mantis/view.php?id=2343 >>> >>> Does anyone have problems with making the changes? >> Hello Kevin, >> I am trying to get an understanding of this proposal. Consider a >> simple module setup: >> >> module parent(); >> electrical a; >> electrical gnd; >> ground gnd; >> wire net; >> >> vdc #(.dc(5)) v0(a,gnd); >> mydig d1(a,net); >> endmodule >> >> module mydig(in,out); >> wire in; input in; >> wire out; output out; >> assign out = in; >> endmodule >> >> >> Currently the connect module (a2d) to convert the electrical net 'a' >> to digital 'in' is inserted in parent. >> Are you proposing that it is inserted in mydig instead? > > Yes, since the "assign" statement is the actual driving process. > But then that will mean I will insert more connect modules than potentially needed. If my parent module instantiates 2 different digital modules mydig_1 d1(a,net); mydig_2 d2(a,net); that both take the continuous net 'a' as an input. In today's flow this would result in 1 connect module being inserted in 'parent' and that output from that connect module being passed to d1 and d2. But this new proposal will result in 2 connect modules being inserted, one in both d1 and d2. I can see that this is the required behaviour if modules mydig_1 and mydig_2 have different power supplies but if they don't then this becomes inefficient. Also if the connect module is inserted in the child module, there is an overhead on the implementation to change all references to the original net 'in' to the output from the connect module. My preference would be to address this problem as well as how to correctly support multiple power supplies and power sensitive connect modules post LRM2.3 in the sub-committee along with the other mixed signal changes. Dave > Kev. > -- ===================================== -- David Miller -- Design Technology (Austin) -- Freescale Semiconductor -- Ph : 512 996-7377 Fax: x7755 ===================================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Apr 2 14:58:38 2008
This archive was generated by hypermail 2.1.8 : Wed Apr 02 2008 - 14:58:40 PDT