On 11/17/20 5:08 PM, Jarkko Nikula wrote: > Add support for M_CAN controller on Intel Elkhart Lake attached to the > PCI bus. It integrates the Bosch M_CAN controller with Message RAM and > the wrapper IP block with additional registers which all of them are > within the same MMIO range. > > Currently only interrupt control register from wrapper IP is used and > the MRAM configuration is expected to come from the firmware via > "bosch,mram-cfg" device property and parsed by m_can.c core. > > Initial implementation is done by Felipe Balbi while he was working at > Intel with later changes from Raymond Tan and me. > > Co-developed-by: Felipe Balbi (Intel) <balbi@xxxxxxxxxx> > Signed-off-by: Felipe Balbi (Intel) <balbi@xxxxxxxxxx> > Co-developed-by: Raymond Tan <raymond.tan@xxxxxxxxx> > Signed-off-by: Raymond Tan <raymond.tan@xxxxxxxxx> > Signed-off-by: Jarkko Nikula <jarkko.nikula@xxxxxxxxxxxxxxx> > --- > This has soft dependency to patches sent earlier by Patrik Flykt and me: > https://www.spinics.net/lists/linux-can/msg04936.html > https://www.spinics.net/lists/linux-can/msg04182.html > Soft dependency since this can be applied without them but will see the > issues fixed by those patches. I've applied the patches to linux-can-next/m_can, which is available here https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/commit/?h=m_can Can you please test that branch. This will go into next, once the net/master is merged to net-next/master. regards, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung West/Dortmund | Phone: +49-231-2826-924 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachment:
signature.asc
Description: OpenPGP digital signature
