Reading a serial data stream with Verilog
You have two requirements here:


You need to make sure you sample that data at the correct time according to the bus needs.
You need to synchronize this data into your system clock domain.


There are a couple of ways to meet these needs.

First, if the bus clock is slow enough below your system clock, then you can synchronize the bus clock to your clock domain with a double flop.  Then use a simple edge detector to determine when the rising edge is.  This is used to safely sample the data line of the bus.  Note that this achieves #2 automatically.  Also, as noted here, this is the preferred way to do this in an FPGA.

This method has a drawback in that the data is sampled somewhere between two and three system clocks later than the actual 'on the pin' bus clock edge.  If this is too long (due to your system clock not being fast enough in comparison), you have to go an alternative way.

In this method, you sample before synchronizing to the system clock domain.  The reason is to make sure you are sampling at the right time according to the bus.

always @(posedge bclk) begin  // positive edge of bus clock
    sampled_data &lt;= data;
end


At this point, you have sampled_data which is a signal in the bclk domain.  You need to synchronize it to your system clock domain.  To do this, you have to use handshaking or a FIFO.

One way that works is to do the shift register in the bus clock domain to get to parallel data.  Then pass it through a dual clock FIFO to the other domain.  FPGAs have primitives just for this use.

// Latch the data in the bclk domain
always @(posedge bclk) begin
    fifo_d &lt;= {fifo_d[30:0], data};

    data_count &lt;= data_count + 1;
    if (data_count == 31)
        fifo_wr &lt;= 1'b1;  // This will latch fifo_d to the dual clock fifo input
    else
        fifo_wr &lt;= 1'b0;
end

// Read the data out of the FIFO in the system clock domain.
always @(posedge clk) begin
    if (fifo_ready)
        synchronized_data &lt;= fifo_q;   // Now the data is in your domain.
end


Other notes:

As with any I/O at the edge of the FPGA as well as between clock domains, you will need to correctly define the timing constraints.  Do describe the details is a bit too general for this forum, but as recommended in the comments by Greg, this paper is a good source for understanding the needs for the clock domain crossing.  The FPGA vendors tend to have decent write ups for input delay and output delay definitions as well.