Bark model Flash Attention 2 Enabling to pass on check_device_map parameter to super()

[damithsenanayake]

What does this PR do?

when using flash_attention_2 with bark model, the _check_and_enable_flash_attn_2() method receives a 'check_device_map' paramter from modeling_utils.py. However it's not passed on to the super and fails execution. The fix simply grabs it from the caller and passes it on to the super.

Fixes # 29332

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@sanchit-gandhi

[ArthurZucker]

LGMT let's make sure CI's are green !

[damithsenanayake]

LGMT let's make sure CI's are green !

Checked! Style fixup was needed and done.

[amyeroberts]

@damithsenanayake Thanks for working on this!

Did you happen to rebase? If so, did you force push? At the moment the branch commit history shows lots of unrelated commits from main, which looks like rebasing without force pushing (this is necessary as rebasing is effectively rewriting the branch history)

[damithsenanayake]

@damithsenanayake Thanks for working on this!

Did you happen to rebase? If so, did you force push? At the moment the branch commit history shows lots of unrelated commits from main, which looks like rebasing without force pushing (this is necessary as rebasing is effectively rewriting the branch history)

Hi, thanks for the clarification. I have rebased the dev branch and git push --force . I still see the unrelated commits (although they seem to be already merged in the upstream main). should I create a separate PR with the most recent fetch/pull?

[damithsenanayake]

@damithsenanayake Thanks for working on this!
Did you happen to rebase? If so, did you force push? At the moment the branch commit history shows lots of unrelated commits from main, which looks like rebasing without force pushing (this is necessary as rebasing is effectively rewriting the branch history)

Hi, thanks for the clarification. I have rebased the dev branch and git push --force . I still see the unrelated commits (although they seem to be already merged in the upstream main). should I create a separate PR with the most recent fetch/pull?

NVM I had to resync the PR. Thanks for your help! :)

[amyeroberts]

Thanks for adding!