public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
	Alan Cox <alan@linux.intel.com>,
	Alessandro Rubini <rubini@gnudd.com>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] c_can_pci: generic module for c_can on PCI
Date: Mon, 04 Jun 2012 18:45:44 +0200	[thread overview]
Message-ID: <1677842.Pq7naXsvrI@harkonnen> (raw)
In-Reply-To: <20120604165619.15ba43bf@pyramind.ukuu.org.uk>

> > +static u16 c_can_pci_read_reg_aligned_to_16bit(struct c_can_priv
> > *priv, +						void *reg)
> 
> I'm a bit worried this function name might be too short ;)

I know :) I was inspired by the same function in c_can_platform.c


About these function I suggest to move them into c_can.c because they 
are the same for c_can_platform.c and c_can_pci.c Then add a new field 
c_can_priv->offset which can be used to shift the register offset 
coherently with the memory alignment. Finally, remove c_can_priv-
>read_reg and c_can_priv->write_reg and use internal c_can.c function to 
read and write registers.

static u16 c_can_read_reg(struct c_can_priv *priv, enum reg index)
{
	return readw(priv->base + (priv->regs[index] << priv->offset));
}
static void c_can_write_reg(struct c_can_priv *priv, enum reg index,
						u16 val)
{
	writew(val, priv->base + (priv->regs[index] << priv->offset));
}


If it's ok, I can made a patch for this in the next days.

> > +	 * do not call pci_disable_device on sta2x11 because it
> > +	 * break all other Bus masters on this EP
> > +	 */
> > +	if(pdev->vendor == PCI_VENDOR_ID_STMICRO &&
> > +	   pdev->device == PCI_DEVICE_ID_STMICRO_CAN)
> > +		goto out;
> 
> Is that the disabling or the dropping it into D3. We have a PCI quirk
> flag for the latter. See "quirk_no_ata_d3". That will also avoid any
> accidents elsewhere. Right now the quirk has "ata" in the name but the
> ata is just historically because we had to quirk various disk
> controllers.

We are investigating if this is still necessary on the current version 
of the board.

-- 
Federico Vaga

  parent reply	other threads:[~2012-06-04 16:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 20:59 [PATCH] STA2X11 CAN: CAN driver for the STA2X11 board Federico Vaga
2012-05-18  6:00 ` Wolfgang Grandegger
2012-05-26  8:36   ` Federico Vaga
2012-05-26 19:57     ` Wolfgang Grandegger
2012-06-04 13:32       ` generic module for c-can on pci Federico Vaga
2012-06-04 13:32         ` [PATCH RFC] c_can_pci: generic module for c_can on PCI Federico Vaga
2012-06-04 14:04           ` Marc Kleine-Budde
2012-06-12 14:25             ` Federico Vaga
2012-06-12 14:46               ` Marc Kleine-Budde
2012-06-12 14:53                 ` Federico Vaga
2012-06-04 15:56           ` Alan Cox
2012-06-04 16:45             ` Alessandro Rubini
2012-06-11 13:51               ` Wolfgang Grandegger
2012-06-11 14:23                 ` Alessandro Rubini
2012-06-04 16:45             ` Federico Vaga [this message]
2012-06-05  3:42               ` Bhupesh SHARMA
2012-06-05 11:19                 ` Federico Vaga
2012-06-05 13:04                   ` Bhupesh SHARMA
2012-06-05 13:13                     ` Alessandro Rubini
2012-06-05 13:21                       ` Marc Kleine-Budde
2012-06-05 13:30                         ` Alessandro Rubini
2012-06-05 15:12                           ` AnilKumar, Chimata
2012-06-05 16:50                             ` Alessandro Rubini
2012-06-06  3:50                               ` Bhupesh SHARMA
2012-06-11 13:18                                 ` Federico Vaga
2012-06-11 14:21                                   ` Wolfgang Grandegger
2012-06-05 13:22                       ` Bhupesh SHARMA
2012-06-11 14:09           ` Wolfgang Grandegger

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=1677842.Pq7naXsvrI@harkonnen \
    --to=federico.vaga@gmail.com \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=giancarlo.asnaghi@st.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=rubini@gnudd.com \
    --cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox