All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Štetiar" <ynezz@true.cz>
To: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Cc: "ynezz@true.cz" <ynezz@true.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"stefan@agner.ch" <stefan@agner.ch>,
	"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"stillcompiling@gmail.com" <stillcompiling@gmail.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	"galak@codeaurora.org" <galak@codeaurora.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>
Subject: Re: [PATCH v2 1/2] ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM
Date: Fri, 8 Jan 2016 09:42:47 +0100	[thread overview]
Message-ID: <20160108084247.GB27359@ibawizard.net> (raw)
In-Reply-To: <1452071716.30372.61.camel@toradex.com>

Marcel Ziswiler <marcel.ziswiler@toradex.com> [2016-01-06 09:15:18]:

> > > <&pinctrl_regulator_usbotg_pwr>;
> > > +			regulator-name = "usb_otg_vbus";
> > > +			regulator-min-microvolt = <5000000>;
> > > +			regulator-max-microvolt = <5000000>;
> > > +			gpio = <&gpio3 22 GPIO_ACTIVE_HIGH>;
> > > +			enable-active-high;
> > > +			status = "disabled";
> > > +		};
> > 
> > I'm not sure, but it seems to me, that we should move this regulator into
> > the carrier board DTS. On our custom carrier board we've this regulator
> > always on and we use this GPIO for heartbeat LED, so I've this in our
> > carrier board DTS[2]:
> 
> Yes, you are absolutely right and e.g. on Apalis T30 [1] that is exactly how
> we did it.

And what about usdhc? It leads to the same overrides in the carrier board
file:

&iomuxc {
	usdhc {
		/* GPIO4_IO20 is LVDS */
		pinctrl_mmc_cd: gpio_mmc_cd {
		};

		/* Used as misc GPIOs */
		pinctrl_usdhc1: usdhc1grp {
		};
	};
};

> > > +/* PAD Ctrl values for common settings */
> > > +/*
> > > + * (PAD_CTL_HYS | PAD_CTL_PUS_100K_UP | PAD_CTL_PUE | PAD_CTL_PKE
> > > |
> > > + *  PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm)
> > > + */
> > > +#define PAD_CTRL_HYS_PU 0x1b0b0
> > 
> > This was requested to be reworked. I've simply replaced all the
> > macros with
> > hex values.
> 
> I don't think the reviewers really concluded on the action to be taken
> on here and just using hex values is probably the most stupid solution.

It's simple, if you just leave it as it is, then it will never get merged.
That's how kernel development works :) We've at least two options here:

1. Follow the old path and just convert those macros to hex values
2. Rework it - move those macros to some header file etc.

-- ynezz

WARNING: multiple messages have this Message-ID (diff)
From: "Petr Štetiar" <ynezz-knWk7/PSn+s@public.gmane.org>
To: Marcel Ziswiler
	<marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
Cc: "ynezz-knWk7/PSn+s@public.gmane.org"
	<ynezz-knWk7/PSn+s@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"pawel.moll-5wv7dgnIgG8@public.gmane.org"
	<pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	"stefan-XLVq0VzYD2Y@public.gmane.org"
	<stefan-XLVq0VzYD2Y@public.gmane.org>,
	"shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"mark.rutland-5wv7dgnIgG8@public.gmane.org"
	<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	"stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org"
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	"galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
	<galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	"shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
	<l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	"kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
	<kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	"linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM
Date: Fri, 8 Jan 2016 09:42:47 +0100	[thread overview]
Message-ID: <20160108084247.GB27359@ibawizard.net> (raw)
In-Reply-To: <1452071716.30372.61.camel-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>

Marcel Ziswiler <marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org> [2016-01-06 09:15:18]:

> > > <&pinctrl_regulator_usbotg_pwr>;
> > > +			regulator-name = "usb_otg_vbus";
> > > +			regulator-min-microvolt = <5000000>;
> > > +			regulator-max-microvolt = <5000000>;
> > > +			gpio = <&gpio3 22 GPIO_ACTIVE_HIGH>;
> > > +			enable-active-high;
> > > +			status = "disabled";
> > > +		};
> > 
> > I'm not sure, but it seems to me, that we should move this regulator into
> > the carrier board DTS. On our custom carrier board we've this regulator
> > always on and we use this GPIO for heartbeat LED, so I've this in our
> > carrier board DTS[2]:
> 
> Yes, you are absolutely right and e.g. on Apalis T30 [1] that is exactly how
> we did it.

And what about usdhc? It leads to the same overrides in the carrier board
file:

&iomuxc {
	usdhc {
		/* GPIO4_IO20 is LVDS */
		pinctrl_mmc_cd: gpio_mmc_cd {
		};

		/* Used as misc GPIOs */
		pinctrl_usdhc1: usdhc1grp {
		};
	};
};

> > > +/* PAD Ctrl values for common settings */
> > > +/*
> > > + * (PAD_CTL_HYS | PAD_CTL_PUS_100K_UP | PAD_CTL_PUE | PAD_CTL_PKE
> > > |
> > > + *  PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm)
> > > + */
> > > +#define PAD_CTRL_HYS_PU 0x1b0b0
> > 
> > This was requested to be reworked. I've simply replaced all the
> > macros with
> > hex values.
> 
> I don't think the reviewers really concluded on the action to be taken
> on here and just using hex values is probably the most stupid solution.

It's simple, if you just leave it as it is, then it will never get merged.
That's how kernel development works :) We've at least two options here:

1. Follow the old path and just convert those macros to hex values
2. Rework it - move those macros to some header file etc.

-- ynezz
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: ynezz@true.cz (Petr Štetiar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM
Date: Fri, 8 Jan 2016 09:42:47 +0100	[thread overview]
Message-ID: <20160108084247.GB27359@ibawizard.net> (raw)
In-Reply-To: <1452071716.30372.61.camel@toradex.com>

Marcel Ziswiler <marcel.ziswiler@toradex.com> [2016-01-06 09:15:18]:

> > > <&pinctrl_regulator_usbotg_pwr>;
> > > +			regulator-name = "usb_otg_vbus";
> > > +			regulator-min-microvolt = <5000000>;
> > > +			regulator-max-microvolt = <5000000>;
> > > +			gpio = <&gpio3 22 GPIO_ACTIVE_HIGH>;
> > > +			enable-active-high;
> > > +			status = "disabled";
> > > +		};
> > 
> > I'm not sure, but it seems to me, that we should move this regulator into
> > the carrier board DTS. On our custom carrier board we've this regulator
> > always on and we use this GPIO for heartbeat LED, so I've this in our
> > carrier board DTS[2]:
> 
> Yes, you are absolutely right and e.g. on Apalis T30 [1] that is exactly how
> we did it.

And what about usdhc? It leads to the same overrides in the carrier board
file:

&iomuxc {
	usdhc {
		/* GPIO4_IO20 is LVDS */
		pinctrl_mmc_cd: gpio_mmc_cd {
		};

		/* Used as misc GPIOs */
		pinctrl_usdhc1: usdhc1grp {
		};
	};
};

> > > +/* PAD Ctrl values for common settings */
> > > +/*
> > > + * (PAD_CTL_HYS | PAD_CTL_PUS_100K_UP | PAD_CTL_PUE | PAD_CTL_PKE
> > > |
> > > + *??PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm)
> > > + */
> > > +#define PAD_CTRL_HYS_PU 0x1b0b0
> > 
> > This was requested to be reworked. I've simply replaced all the
> > macros with
> > hex values.
> 
> I don't think the reviewers really concluded on the action to be taken
> on here and just using hex values is probably the most stupid solution.

It's simple, if you just leave it as it is, then it will never get merged.
That's how kernel development works :) We've at least two options here:

1. Follow the old path and just convert those macros to hex values
2. Rework it - move those macros to some header file etc.

-- ynezz

  reply	other threads:[~2016-01-08  8:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 16:39 [PATCH v2 0/2] ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM/Ixora carrier board Marcel Ziswiler
2016-01-05 16:39 ` Marcel Ziswiler
2016-01-05 16:39 ` Marcel Ziswiler
2016-01-05 16:39 ` [PATCH v2 1/2] ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM Marcel Ziswiler
2016-01-05 16:39   ` Marcel Ziswiler
2016-01-06  8:03   ` Petr Štetiar
2016-01-06  8:03     ` Petr Štetiar
2016-01-06  8:03     ` Petr Štetiar
2016-01-06  9:15     ` Marcel Ziswiler
2016-01-06  9:15       ` Marcel Ziswiler
2016-01-06  9:15       ` Marcel Ziswiler
2016-01-08  8:42       ` Petr Štetiar [this message]
2016-01-08  8:42         ` Petr Štetiar
2016-01-08  8:42         ` Petr Štetiar
2016-01-08 10:59         ` Marcel Ziswiler
2016-01-08 10:59           ` Marcel Ziswiler
2016-01-08 10:59           ` Marcel Ziswiler
2016-01-07  6:29   ` Stefan Agner
2016-01-07  6:29     ` Stefan Agner
2016-01-08  8:28     ` Marcel Ziswiler
2016-01-08  8:28       ` Marcel Ziswiler
2016-01-08  8:28       ` Marcel Ziswiler
2016-01-08  8:57   ` Petr Štetiar
2016-01-08  8:57     ` Petr Štetiar
2016-01-08  8:57     ` Petr Štetiar
2016-01-08 10:59     ` Marcel Ziswiler
2016-01-08 10:59       ` Marcel Ziswiler
2016-01-08 10:59       ` Marcel Ziswiler
2016-01-05 16:39 ` [PATCH v2 2/2] ARM: dts: imx6: Add support for Toradex Ixora carrier board Marcel Ziswiler
2016-01-05 16:39   ` Marcel Ziswiler
2016-01-07  6:38   ` Stefan Agner
2016-01-07  6:38     ` Stefan Agner
2016-01-07  6:38     ` Stefan Agner
2016-01-08  8:29     ` Marcel Ziswiler
2016-01-08  8:29       ` Marcel Ziswiler
2016-01-08  8:29       ` Marcel Ziswiler

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=20160108084247.GB27359@ibawizard.net \
    --to=ynezz@true.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marcel.ziswiler@toradex.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=stillcompiling@gmail.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.