You need to tell us more.

Are you hooking the 8255 (where did you get it, perhaps it's actually 8255A?) to the 8052 as a peripheral with R/W signals? What is your address latch?

If you are using an 8255A hooked to a real 22 MHz 8052 with a 74ALS373 address latch, then it simply won't work. It can't be fixed in software unless you have a variant that can specify wait states. (But you wrote 8052).

It gets even worse with 8052 variants which run on fewer than 12 crystal clocks per cycle. Is the 8052 a real 12-cycle part; or is it a six-, three-, two-, or 1- cycle variant?

If you have a fast 8052 and still must interface to a slow peripheral, then you might find that the simplest way is to draw vertical lines on the 8255A data sheet R/W timing and set all of the signals, in order, to satisfy the waveforms.

If someone gave you some 8255's as a gift, thank him and frame them in your personal museum.

If this is a homework assignment, you may wish to diplomatically request the instructor to explain the purpose in using this 25 year old part which is not used in industry any more. (Beware, the instructor may assign you to select a better example. :-) )