Searched refs:ts_fw_log_sector_sz (Results 1 – 2 of 2) sorted by relevance
262 (state->ts_fw_device_sz >> state->ts_fw_log_sector_sz)) { in tavor_ioctl_flash_read()273 &ioctl_info.tf_sector[0], 1 << state->ts_fw_log_sector_sz, in tavor_ioctl_flash_read()376 (state->ts_fw_device_sz >> state->ts_fw_log_sector_sz)) { in tavor_ioctl_flash_write()383 &state->ts_fw_sector[0], 1 << state->ts_fw_log_sector_sz, in tavor_ioctl_flash_write()465 (state->ts_fw_device_sz >> state->ts_fw_log_sector_sz)) { in tavor_ioctl_flash_erase()541 state->ts_fw_log_sector_sz, KM_SLEEP); in tavor_ioctl_flash_init()641 kmem_free(state->ts_fw_sector, 1 << state->ts_fw_log_sector_sz); in tavor_ioctl_flash_cleanup_nolock()1329 addr = sector_num << state->ts_fw_log_sector_sz; in tavor_flash_read_sector()1330 end_addr = addr + (1 << state->ts_fw_log_sector_sz); in tavor_flash_read_sector()1373 addr = sector_num << state->ts_fw_log_sector_sz; in tavor_flash_write_sector()[all …]
584 uint32_t ts_fw_log_sector_sz; member598 tavor_state_s::ts_fw_log_sector_sz608 tavor_state_s::ts_fw_log_sector_sz