Remove prints from VExpress NOR flash driver
There are way too many flash accesses for these prints to be useful.
As a result, they clobber the output (when they are enabled). They
might have been useful when the driver was developed but now that
it is more mature, their existence is arguable.
Change-Id: Ie068000ad2319c5f58f8bb7c7c891a24f6d21fdf
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
diff --git a/drivers/io/vexpress_nor/io_vexpress_nor_hw.c b/drivers/io/vexpress_nor/io_vexpress_nor_hw.c
index de7b4ce..6e563c9 100644
--- a/drivers/io/vexpress_nor/io_vexpress_nor_hw.c
+++ b/drivers/io/vexpress_nor/io_vexpress_nor_hw.c
@@ -159,7 +159,6 @@
int err = IO_SUCCESS;
uint32_t status_register;
- VERBOSE("%s : 0x%x\n", __func__, block_offset);
/* Request a block erase and then confirm it */
nor_send_cmd(block_offset, NOR_CMD_BLOCK_ERASE);
nor_send_cmd(block_offset, NOR_CMD_BLOCK_ERASE_ACK);
@@ -359,7 +358,6 @@
/* address passed should be block aligned */
assert(!(offset % fp->block_spec->block_size));
- VERBOSE("%s : 0x%x\n", __func__, flash_pos);
/* Unlock block */
flash_unlock_block_if_necessary(fp->block_spec, block_offset);
@@ -398,7 +396,6 @@
*written = fp->block_spec->block_size;
lock_block:
- VERBOSE("%s : 0x%x\n", __func__, block_offset);
/* Lock the block once done */
flash_perform_lock_operation(fp->block_spec,
block_offset,