On Thu, Nov 2, 2023 at 5:22 AM <conor.doo...@microchip.com> wrote: > > On 01/11/2023 18:01, Saravanan.K.S wrote: > > [Some people who received this message don't often get email from > > saravanan.kadambathursubramani...@windriver.com. Learn why this is > > important at https://aka.ms/LearnAboutSenderIdentification ] > > > > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > > content is safe > > > > From: Conor Dooley <conor.doo...@microchip.com> > > > > commit 51b0ed2098daf7579d67b6b0aa218f2794d3c87a from > > https://github.com/linux4microchip/linux.git linux-6.1-mchp > > > > Add support for the "generic" services on the PolarFire SoC. > > > > The PolarFire SoC system controller is communicated with via a mailbox. > > Several of the functions provided by the system controller do not belong > > in a specific subsystem, such as reading the fpga device certificate. > > These "generic" services all follow the same format: > > - a command + optional payload sent to the sys controller > > - a status + a payload returned to Linux > > > > Add a driver to implement these services and export an interface > > as a char device. > > > > Reviewed-by: Daire McNamara <daire.mcnam...@microchip.com> > > Signed-off-by: Conor Dooley <conor.doo...@microchip.com> > > Signed-off-by: Saravanan.K.S > > <saravanan.kadambathursubramani...@windriver.com> > > I've been CC'ed on 90% of this thread, but not the cover letter & I cannot > find it on an archive site either - what's the goal of this series? > Some of the later patches in the series (auto update & the pac193x drivers > in particular) are going have their userspace interfaces change when > landing in mainline too - I'm not sure if or how that affects your > objectives, but I figured I'd point it out. > Also there are some not-yet-mainline dt-bindings in here, so that side > of things is also subject to change too.
Hmm. Sorry about the noise. I'm not the submitter (obviously), but I am the maintainer being targeted to queue the WIP patches. Since this is a Yocto project sent to stage a BSP, they should have never been copied to you. Saravanan: you need to check your git configuration and make sure --suppress-cc is appropriately used to not spam unsuspecting patch authors. Conor: Thanks for the feedback on the changes, it is appreciated that you took the time to reply even after all of the unexpected email arrival. I'll leave it up to Saravanan to address any details, but I can say that we'll only keep this around for the duration of the yocto 6.1 reference kernel's support window, and would take rebased / new patches when carrying it forward. The consumers of the BSP would need to be aware that interfaces and bindings will change as they follow it forward. Bruce > > Cheers, > Conor. > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13260): https://lists.yoctoproject.org/g/linux-yocto/message/13260 Mute This Topic: https://lists.yoctoproject.org/mt/102357553/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
