public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 5/6] ARM: imx: pinctrl: Add support for i.MX2[38] mxs pinctrl driver
Date: Wed, 19 Jun 2019 08:51:02 +0200	[thread overview]
Message-ID: <20190619085102.7f604022@jawa> (raw)
In-Reply-To: <b600fc17-6b09-af98-19a7-36aab92a85b3@denx.de>

Hi Marek,

> On 6/19/19 12:01 AM, Lukasz Majewski wrote:
> > The code responsible for setting proper values in the MUX registers
> > (in the mxs_pinctrl_set_state()) has been ported from Linux kernel
> > - SHA1: 17bb763e7eaf tag v5.1.11 from linux-stable.  
> 
> Maybe you want to keep the DTs and this driver based off the same
> version of Linux kernel.

I will keep and used the v5.1.11 in both drivers.

> 
> Tags are "pinctrl: mxs: ".

I will fix the tags globally.

> 
> > As the pinctrl node in the imx28.dtsi file has gpio pins nodes as
> > subnodes, it was necessary to use 'dm_scan_fdt_dev()' (as a .bind
> > method) to also make them 'visible' by the DM's "gpio_mxs" driver.
> > 
> > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> >   
> 
> [...]
> 
> > +static void mxs_pinctrl_rmwl(u32 value, u32 mask, u8 shift, void
> > __iomem *reg) +{
> > +	u32 tmp;  
> 
> This is clrsetbits_le32() reimplementation.

Ach, right. I will leave the mxs_pinctrl_rmwl wrapper function and
replace below code with clrsetbits_le32.

> 
> > +	tmp = readl(reg);
> > +	tmp &= ~(mask << shift);
> > +	tmp |= value << shift;
> > +	writel(tmp, reg);
> > +}  
> [...
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190619/a808f0b2/attachment.sig>

  reply	other threads:[~2019-06-19  6:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 22:01 [U-Boot] [PATCH v4 0/6] DM: Convert i.MX28 gpio, pinmux, spi and eth drivers to DM/DTS Lukasz Majewski
2019-06-18 22:01 ` [U-Boot] [PATCH v4 1/6] ARM: dts: imx: Copy imx28 device tree related files from Linux kernel (v5.1.9) Lukasz Majewski
2019-06-18 22:01 ` [U-Boot] [PATCH v4 2/6] ARM: imx: net: Enable support for i.MX28 DM_ETH in the fec_mxc.c driver Lukasz Majewski
2019-06-18 22:10   ` Marek Vasut
2019-06-18 22:01 ` [U-Boot] [PATCH v4 3/6] DTS: dm: mxs: gpio: Provide 'gpio-ranges' for mxs_gpio driver Lukasz Majewski
2019-06-18 22:07   ` Marek Vasut
2019-06-18 22:01 ` [U-Boot] [PATCH v4 4/6] ARM: dm: mxs: gpio: Add support for DM/DTS in the mxs_gpio.c driver (DM_GPIO) Lukasz Majewski
2019-06-18 22:11   ` Marek Vasut
2019-06-18 22:01 ` [U-Boot] [PATCH v4 5/6] ARM: imx: pinctrl: Add support for i.MX2[38] mxs pinctrl driver Lukasz Majewski
2019-06-18 22:13   ` Marek Vasut
2019-06-19  6:51     ` Lukasz Majewski [this message]
2019-06-18 22:01 ` [U-Boot] [PATCH v4 6/6] ARM: dm: spi: Add support DM/DTS for i.MX28 mxs SPI driver (DM_SPI conversion) Lukasz Majewski
2019-06-18 22:16   ` Marek Vasut
2019-06-19  6:52     ` Lukasz Majewski
2019-06-19 10:30       ` Marek Vasut

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=20190619085102.7f604022@jawa \
    --to=lukma@denx.de \
    --cc=u-boot@lists.denx.de \
    /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