This looks reasonable to me, it's not something we require for Ethos-N but I can see why it may be desirable. I am noticing quite a bit of API creep around BYOC though. We never really settled on a way to encapsulate the partitioning passes and now we have another special pass that may or may not need to run + a new config option. Is there a way we can abstract some of this implementation detail away so a user who just wants to compile for 'DNNL' doesn't need intimate knowledge of the BYOC infrastructure?
--- [Visit Topic](https://discuss.tvm.ai/t/rfc-byoc-data-calibration-flow/7099/8) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/ba6bd7b73e2fb7d493e24f96d3e4caad5c1d89ab4d32ab78efee6f06ab8e21b2).
