From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 00/12] Add support for pinmux status command on beaglebone
Date: Fri, 5 Feb 2021 13:37:46 -0500 [thread overview]
Message-ID: <20210205183746.GC10169@bill-the-cat> (raw)
In-Reply-To: <a93affaa-3c37-f8ed-c57a-a7e98f51f642@ti.com>
On Fri, Feb 05, 2021 at 07:47:19PM +0530, Lokesh Vutla wrote:
> +Tom
>
> On 05/02/21 4:24 pm, Dario Binacchi wrote:
> > Hi Lokesh,
> >
> >> Il 04/02/2021 19:02 Lokesh Vutla <lokeshvutla@ti.com> ha scritto:
> >>
> >>
> >> On 29/01/21 3:54 am, Dario Binacchi wrote:
> >>>
> >>> The series was born from the need to check the pinmux setting of a
> >>> peripheral on a beaglebone board. I then ran the 'pinmux status -a'
> >>> command but it failed because some operations (get_pin_muxing,
> >>> get_pin_name and get_pins_count) were missing in the 'pinctrl-single'
> >>> driver.
> >>>
> >>> The patch series can be cleanly applied to the HEAD of the master which
> >>> at the time of release points to 8b195f4b71
> >>> ("Merge https://gitlab.denx.de/u-boot/custodians/u-boot-marvell") commit
> >>
> >> Sandbox tests are failing with this series. Can you take a look?
> >> https://gitlab.denx.de/u-boot/custodians/u-boot-ti/-/jobs/217033
> >>
> >
> > I applied the series to both the "master" branch of u-boot and the "for-rc"
> > branch of u-boot-ti.
> > In both cases, no test fails.
> >
> > Here's how I ran the tests (u-boot-ti case):
> >
> > git clone https://gitlab.denx.de/u-boot/custodians/u-boot-ti.git
> > cd u-boot-ti/
> > git checkout -b for-rc origin/for-rc
> > git am ~/Downloads/Add-support-for-pinmux-status-command-on-beaglebone.patch
> > virtualenv -p /usr/bin/python3 /tmp/venv
> > . /tmp/venv/bin/activate
> > pip install -r test/py/requirements.txt
> > ./test/py/test.py -ra --bd sandbox --build
> >
> > ...
> > =========== 719 passed, 81 skipped in 117.37s (0:01:57) =========
>
> You are right. I tried these locally and I could not reproduce. But the
> gitlab-ci is throwing the same error anytime I push this series.
>
> Simon, Tom,
> Any idea why this could happen?
Since GitLab/Azure are just running it in Docker, what happens if you
run it locally that way?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210205/a80e698d/attachment.sig>
prev parent reply other threads:[~2021-02-05 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 22:24 [PATCH v2 00/12] Add support for pinmux status command on beaglebone Dario Binacchi
2021-01-28 22:24 ` [PATCH v2 01/12] pinctrl: single: fix format of structure documentation Dario Binacchi
2021-01-28 22:24 ` [PATCH v2 02/12] pinctrl: single: fix the loop counter variable type Dario Binacchi
2021-01-28 22:24 ` [PATCH v2 03/12] pinctrl: single: fix offset management Dario Binacchi
2021-01-29 16:50 ` Pratyush Yadav
2021-01-28 22:24 ` [PATCH v2 04/12] pinctrl: single: fix debug messages formatting Dario Binacchi
2021-01-29 16:53 ` Pratyush Yadav
2021-01-28 22:24 ` [PATCH v2 05/12] pinctrl: single: get register area size by device API Dario Binacchi
2021-01-29 17:47 ` Pratyush Yadav
2021-01-28 22:24 ` [PATCH v2 06/12] pinctrl: single: check "register-width" DT property Dario Binacchi
2021-01-28 22:24 ` [PATCH v2 07/12] pinctrl: single: change function mask default value Dario Binacchi
2021-02-01 20:44 ` Simon Glass
2021-01-28 22:24 ` [PATCH v2 08/12] pinctrl: single: add register access functions Dario Binacchi
2021-02-01 20:44 ` Simon Glass
2021-01-28 22:24 ` [PATCH v2 09/12] pinctrl: single: add get_pins_count operation Dario Binacchi
2021-01-28 22:24 ` [PATCH v2 10/12] pinctrl: single: add get_pin_name operation Dario Binacchi
2021-01-28 22:25 ` [PATCH v2 11/12] pinctrl: single: add get_pin_muxing operation Dario Binacchi
2021-02-01 20:44 ` Simon Glass
2021-01-28 22:25 ` [PATCH v2 12/12] test: pinmux: add test for 'pinctrl-single' driver Dario Binacchi
2021-02-04 18:02 ` [PATCH v2 00/12] Add support for pinmux status command on beaglebone Lokesh Vutla
2021-02-05 10:54 ` Dario Binacchi
2021-02-05 14:17 ` Lokesh Vutla
2021-02-05 18:37 ` Tom Rini [this message]
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=20210205183746.GC10169@bill-the-cat \
--to=trini@konsulko.com \
--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