Bug 209277 - powerpc: obsolete driver: Marvell MV64X60 MPSC
Summary: powerpc: obsolete driver: Marvell MV64X60 MPSC
Status: CLOSED CODE_FIX
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: PPC-32 (show other bugs)
Hardware: All Linux
: P1 enhancement
Assignee: platform_ppc-32
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-15 14:09 UTC by Necip Fazil Yildiran
Modified: 2022-06-06 14:47 UTC (History)
6 users (show)

See Also:
Kernel Version: 5.9-rc4
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Necip Fazil Yildiran 2020-09-15 14:09:45 UTC 

    


    


      



        
          Comment 1
        

        
          Necip Fazil Yildiran

        

        
        

        
          2020-09-15 14:25:08 UTC
        

      






The config MV64X60 in arch/powerpc/platforms/embedded6xx/Kconfig is 
non-prompt selected nowhere -- thus, cannot be enabled.
 
In addition, a few other configs cannot be enabled due to their dependency
on MV64X60, e.g., EDAC_MV64X60.
 
The last to use this driver was by PrPMC 280/2800, for which the support
was ended with the commit 3c8464a9b12b 
("powerpc: Delete old PrPMC 280/2800 support").
 
This looks like the related configs (e.g., MV64X60, EDAC_MV64X60) and the
code (e.g., drivers/edac/mv64x60_edac.c) for Marvell MV64X60 MPSC are now
obsolete.

    


    

    

    


      



        
          Comment 4
        

        
          Christophe Leroy

        

        
        

        
          2021-06-19 06:37:37 UTC
        

      






The watchdog patch is flagged 'accepted' in patchwork, should go into 5.14

    


    


      



        
          Comment 5
        

        
          Michael Ellerman

        

        
        

        
          2022-06-06 14:47:22 UTC
        

      






The watchdog driver was removed in:
  bc65baf73b68 ("watchdog: Remove MV64x60 watchdog driver")

    



  






  


    

      

        

          
            

              Note
              You need to
              log in
              before you can comment on or make changes to this bug.