DSA .port_{f,m}db_{add,del} with offloaded LAG interface on mv88e6xxx

Hi,

What happens if a FDB entry is added manually to an offloaded LAG
interface? Does DSA core simply call .port_fdb_add with the member
ports in the LAG?

I'm asking because there is a trunk field in struct
mv88e6xxx_atu_entry, when it is true, the portvec is actually the
trunk ID.
As the current implementation (mv88e6xxx_port_db_load_purge) does not
use this field, it probably won't work.

Regards,
Qingfang