Fix quantized_w8a32_conv1d fusion and operator

[ethansfng]

Summary:

1. Python fusion pass (fusion_pass.py): The permute nodes created in
   get_args_and_kwargs_mixed_w8a32_conv were missing val metadata, causing
   SpecViolationError during ExportedProgram validation. Added val computation
   using fake_mode, matching the pattern used by AddmmPattern.

2. C++ operators (generic + HiFi): cnn_step was called once with wrong
   dimensions (input length instead of kernel_size for d1), only producing
   out_channels values instead of the full output. Fixed to loop over output
   time steps, calling cnn_step per position with correct kernel_size, then
   scattering to NCL output layout.

Differential Revision: D92565258

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/17290

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures

As of commit 6548d79 with merge base f4ef59f ():

NEW FAILURES - The following jobs have failed:

• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / test-moshi-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 114a213815b20209b81f994aac600c8ea864e3dbb722a23ce70c62ae5bb9b201 /exec failed with exit code 1
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t b6b18b17647f31a76aa21686b26d8700f3d6af9f04f7351ced2965beacfd44a2 /exec failed with exit code 1
• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 59cc98f667da488ca15431efcfd7218cdf656aa202f78cc3aae899561bb2deb1 /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@ethansfng has exported this pull request. If you are a Meta employee, you can view the originating Diff in D92565258.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.