All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-can@vger.kernel.org, Chee Hou Ong <chee.houx.ong@intel.com>,
	Aman Kumar <aman.kumar@intel.com>,
	Pallavi Kumari <kumari.pallavi@intel.com>,
	Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
	Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Subject: PCH_CAN removal?
Date: Thu, 19 May 2022 21:15:23 +0200	[thread overview]
Message-ID: <03e3db49-1e56-1e34-ba8d-72ca06019287@hartkopp.net> (raw)
In-Reply-To: <2637cf42-b7da-a862-c599-ce418645629b@linux.intel.com>

Hi Jarkko,

I'm very happy to see that you are cleaning up some custom M_CAN stuff 
which turns out to be already supported ;-)

In fact there is a pch_can (PCI) driver which was used in an Intel 
embedded setup "Topcliff PCH" ~11 years ago. The driver was originally 
contributed by OKI.

And I was pretty sure that this driver implements a C_CAN IP core with a 
PCI binding which is now implemented in the C_CAN_PCI driver.

As I do not have that hardware anymore it would be interesting to see if 
you could bring the PCH board to life with the C_CAN_PCI driver?!?

That would allow us to remove the (then definitely) obsolete pch_can driver.

Thanks & best regards,
Oliver

  reply	other threads:[~2022-05-19 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 13:08 [PATCH net 0/2] pull-request: can 2022-05-13 Marc Kleine-Budde
2022-05-13 13:08 ` [PATCH net 1/2] Revert "can: m_can: pci: use custom bit timings for Elkhart Lake" Marc Kleine-Budde
2022-05-13 17:21   ` Jakub Kicinski
2022-05-14 19:00     ` Marc Kleine-Budde
2022-05-18 12:47     ` Jarkko Nikula
2022-05-19 19:15       ` Oliver Hartkopp [this message]
2022-05-20 12:48         ` PCH_CAN removal? Jarkko Nikula
2022-05-20 14:24           ` Oliver Hartkopp
2022-05-13 13:08 ` [PATCH net 2/2] can: m_can: remove support for custom bit timing, take #2 Marc Kleine-Budde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03e3db49-1e56-1e34-ba8d-72ca06019287@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=aman.kumar@intel.com \
    --cc=chee.houx.ong@intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=kumari.pallavi@intel.com \
    --cc=linux-can@vger.kernel.org \
    --cc=masa-korg@dsn.okisemi.com \
    --cc=tomoya-linux@dsn.okisemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.